Triple
T14159522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Dacia |
E350899
|
entity |
| Predicate | finalConquestYear |
P3478
|
FINISHED |
| Object | 106 AD |
—
|
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: 106 AD | Statement: [Kingdom of Dacia, finalConquestYear, 106 AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalConquestYear Context triple: [Kingdom of Dacia, finalConquestYear, 106 AD]
-
A.
conquestYear
chosen
Indicates the year in which one entity successfully conquered or took control over another entity.
-
B.
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.
-
C.
battleEndYear
Indicates the calendar year in which a particular battle or military engagement concluded.
-
D.
conquestPeriod
Indicates the time span during which one entity successfully subjugates or takes control of another through conquest.
-
E.
yearDefeated
Indicates the specific year in which one entity defeated or overcame another in a competitive or conflict-related context.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61393f308190bb357e2bd1916f94 |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:58 a.m.