Triple
T30221044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Sambre |
E768344
|
entity |
| Predicate | RomanForcesCommandedBy |
P48696
|
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: [Battle of the Sambre, RomanForcesCommandedBy, Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanForcesCommandedBy Context triple: [Battle of the Sambre, RomanForcesCommandedBy, Julius Caesar]
-
A.
RomanCommander
chosen
Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
-
B.
RomanLeaderTitle
Indicates that an entity holds or is associated with an official leadership title within the context of ancient Roman authority or governance.
-
C.
NumidianCommander
Indicates that an entity serves as a military commander associated with Numidia or Numidian forces.
-
D.
GallicCommander
Indicates a person who holds a commanding or leadership role over Gallic forces or within a Gallic context.
-
E.
CimbriTeutonesCommander
Indicates that a person served as a military commander of the Cimbri and Teutones.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 7:35 p.m.