Triple
T7001655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvetii |
E162350
|
entity |
| Predicate | attemptedMigration |
P58482
|
FINISHED |
| Object | 58 BC |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 58 BC | Statement: [Helvetii, attemptedMigration, 58 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedMigration Context triple: [Helvetii, attemptedMigration, 58 BC]
-
A.
enabledMigrationOf
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
B.
attemptedRestoration
Indicates an action where an entity makes an effort to restore or return another entity to a previous or desired state, condition, or form, regardless of whether the restoration succeeds.
-
C.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
D.
attemptedAction
chosen
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
E.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.