Triple
T32339201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Constantinople of 536 |
E826261
|
entity |
| Predicate | heldUnderEmperor |
P9805
|
FINISHED |
| Object | Justinian I |
—
|
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: Justinian I | Statement: [Council of Constantinople of 536, heldUnderEmperor, Justinian I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldUnderEmperor Context triple: [Council of Constantinople of 536, heldUnderEmperor, Justinian I]
-
A.
formedUnderEmperor
Indicates that an entity (such as a group, institution, or administrative unit) was created or established during the reign or authority of a specific emperor.
-
B.
concludedUnderEmperor
Indicates that an event, agreement, or process was completed or formally concluded during the reign of a specific emperor.
-
C.
hasDateUnderEmperor
chosen
Indicates that an event or record occurred during the reign of a specified emperor.
-
D.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
E.
heldUnderCivilRuler
Indicates that an event, position, or status occurred while a particular civil ruler was in power or authority.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1f3a648190802496b36cf767f6 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:48 a.m.