Triple
T28122380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip I of Courtenay |
E710827
|
entity |
| Predicate | reignAsTitularEmperorEnd |
P172810
|
FINISHED |
| Object | 1283 |
—
|
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: 1283 | Statement: [Philip I of Courtenay, reignAsTitularEmperorEnd, 1283]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsTitularEmperorEnd Context triple: [Philip I of Courtenay, reignAsTitularEmperorEnd, 1283]
-
A.
reignAsTitularEmperorStart
Indicates the point in time when an individual begins to hold the title and status of emperor in name, without necessarily exercising actual governing power.
-
B.
reignAsHolyRomanEmperorEnd
Indicates the time or event at which an entity’s tenure as Holy Roman Emperor comes to an end.
-
C.
reignAsKingOfTheRomansEnd
Indicates the point in time or event at which an individual's reign as King of the Romans comes to an end.
-
D.
reignAsLatinEmperorEnd
Indicates the time or event at which an individual’s tenure as Latin Emperor comes to an end.
-
E.
coEmperorEnd
Indicates that one entity’s tenure as co-emperor with another entity comes to an end at a specific point in time.
- F. None of above. chosen
Provenance (4 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 27, 2026, 9:18 p.m.