Triple
T23418114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman province of Gallia |
E560569
|
entity |
| Predicate | conquestEndDate |
P3478
|
FINISHED |
| Object | 51 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: 51 BC | Statement: [Roman province of Gallia, conquestEndDate, 51 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conquestEndDate Context triple: [Roman province of Gallia, conquestEndDate, 51 BC]
-
A.
conquestYear
chosen
Indicates the year in which one entity successfully conquered or took control over another entity.
-
B.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
C.
afterConquestBy
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
D.
invasionEndDate
Indicates the date on which an invasion event is considered to have ended.
-
E.
battleEndYear
Indicates the calendar year in which a particular battle or military engagement concluded.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5438ac08190a40a3d6402794699 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.