Triple
T38094396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Empire under Trajan and Hadrian |
E951203
|
entity |
| Predicate | provinceAdded |
P97574
|
FINISHED |
| Object | Dacia |
—
|
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: Dacia | Statement: [Roman Empire under Trajan and Hadrian, provinceAdded, Dacia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceAdded Context triple: [Roman Empire under Trajan and Hadrian, provinceAdded, Dacia]
-
A.
provinceSupplied
Indicates that a province is provided, furnished, or supplied by a specified source or entity.
-
B.
provinceName
Indicates that a province entity is associated with its specific name as a textual label.
-
C.
provinceCreatedBy
chosen
Indicates that a province was established, formed, or officially created through the action, decision, or authority of a specified agent or entity.
-
D.
provinceExistedFrom
Indicates the starting point in time from which a province began to exist or was officially established.
-
E.
province
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:21 p.m.