Triple

T2293228
Position Surface form Disambiguated ID Type / Status
Subject Dacian tribes E51551 entity
Predicate resultOfConquest P32946 FINISHED
Object creation of Roman province of Dacia 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: creation of Roman province of Dacia | Statement: [Dacian tribes, resultOfConquest, creation of Roman province of Dacia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resultOfConquest
Context triple: [Dacian tribes, resultOfConquest, creation of Roman province of Dacia]
  • A. conqueredIn
    Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
  • B. afterConquestBy chosen
    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. conquestEvent
    Indicates an event in which one party gains control over another entity or territory through force or domination.
  • D. resultOfBattle
    Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
  • E. conqueredCity
    Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
  • 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_69a88b09c644819090b503456d96bf70 completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abcd0e42248190ada33b84d75caa64 completed March 7, 2026, 7 a.m.
PD Predicate disambiguation batch_69abc589295c819092989820c2b4e9d8 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:48 p.m.