Triple
T28661804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothic War (249–251) |
E725486
|
entity |
| Predicate | duringReignOf |
P88085
|
FINISHED |
| Object | Emperor Decius |
—
|
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: Emperor Decius | Statement: [Gothic War (249–251), duringReignOf, Emperor Decius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duringReignOf Context triple: [Gothic War (249–251), duringReignOf, Emperor Decius]
-
A.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
-
B.
builtDuringReignOf
Indicates that something was constructed while a particular ruler or authority was in power.
-
C.
modifiedDuringReignOf
Indicates that an entity was altered, updated, or changed while a particular ruler or authority was in power.
-
D.
activeInReignOf
chosen
Indicates that an entity was active or operational during the time period corresponding to a specific ruler’s reign.
-
E.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:58 a.m.