Triple
T3283305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qart Hadasht |
E68922
|
entity |
| Predicate | roleForHannibal |
P22409
|
FINISHED |
| Object | base before campaigns against Rome |
—
|
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: base before campaigns against Rome | Statement: [Qart Hadasht, roleForHannibal, base before campaigns against Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleForHannibal Context triple: [Qart Hadasht, roleForHannibal, base before campaigns against Rome]
-
A.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
roleAtTrafalgar
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
-
C.
notableRiverCrossingRole
Indicates that an entity plays a significant role as a location or feature involved in the crossing of a river.
-
D.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
roleDuringConquest
chosen
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03621608190a2b7a6b38d6559da |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.