Triple
T28718778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallic coalition |
E730032
|
entity |
| Predicate | primaryEnemyCommander |
P1698
|
FINISHED |
| Object | Julius Caesar |
—
|
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: Julius Caesar | Statement: [Gallic coalition, primaryEnemyCommander, Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEnemyCommander Context triple: [Gallic coalition, primaryEnemyCommander, Julius Caesar]
-
A.
primaryEnemy
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
B.
opposingCommander
chosen
Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
-
C.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
-
D.
primaryOpposingCommanderUS
Indicates that the referenced person is the main opposing military commander of the United States in a given conflict or operation.
-
E.
commanderAttacker
Indicates that one entity serves as the commanding officer or leader of another entity that is acting as the attacker in a conflict or operation.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: April 28, 2026, 5:52 a.m.