Triple
T8896514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dacia |
E211817
|
entity |
| Predicate | romanProvinceEstablished |
P73521
|
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: [Dacia, romanProvinceEstablished, 106 AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanProvinceEstablished Context triple: [Dacia, romanProvinceEstablished, 106 AD]
-
A.
romanProvinceAfterConquest
chosen
Indicates that a territory became a Roman province following its military conquest by Rome.
-
B.
RomanProvinceContext
Indicates that the subject entity is situated within, associated with, or understood in the administrative and cultural framework of a Roman province.
-
C.
foundedInEmpire
Indicates that an entity (such as an organization, city, or institution) was established during the existence or rule of a specified empire.
-
D.
laterRomanAdministrativeUnit
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
-
E.
modernProvinceLocation
Indicates that a historical or former province is located within a specified modern administrative province or region.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61bfec0881908e4ef5b7f0e6b542 |
completed | April 1, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.