Triple
T30021216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Nemanjić |
E762744
|
entity |
| Predicate | reignAsKing |
P10353
|
FINISHED |
| Object | 1217–1228 |
—
|
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: 1217–1228 | Statement: [Stefan Nemanjić, reignAsKing, 1217–1228]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsKing Context triple: [Stefan Nemanjić, reignAsKing, 1217–1228]
-
A.
reignAs
chosen
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
B.
reignAsKingEnd
Indicates the point in time or event at which an entity’s period of reigning as king comes to an end.
-
C.
reignStartAsKing
Indicates the time or event at which an individual begins their reign in the role of king.
-
D.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
E.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 6:47 p.m.