Triple
T31684861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio XIX |
E808630
|
entity |
| Predicate | sharedFateWith |
P151025
|
FINISHED |
| Object | Legio XVII |
—
|
NE NERFINISHED |
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: Legio XVII | Statement: [Legio XIX, sharedFateWith, Legio XVII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedFateWith Context triple: [Legio XIX, sharedFateWith, Legio XVII]
-
A.
sharesFateWith
chosen
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
-
B.
sharesSlainWith
Indicates that two or more entities have killed the same target or share responsibility for the same slaying event.
-
C.
sharesImmortalityWith
Indicates that one entity grants or mutually possesses an immortal or deathless state together with another entity.
-
D.
sharesProtagonistWith
Indicates that two narrative works feature the same main protagonist character.
-
E.
sharesCharacterWith
Indicates that two entities have at least one character (such as a letter, symbol, or glyph) in common.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 30, 2026, 11:06 p.m.