Triple
T15494907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine III |
E378791
|
entity |
| Predicate | coReignStartWithHeraclius |
P50172
|
FINISHED |
| Object | 613 |
—
|
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: 613 | Statement: [Constantine III, coReignStartWithHeraclius, 613]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coReignStartWithHeraclius Context triple: [Constantine III, coReignStartWithHeraclius, 613]
-
A.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignAsKingOfTheRomansStart
Indicates the point in time when an individual begins their reign as King of the Romans.
-
C.
reignStartAsKingOfWestFrancia
Indicates the date or event when an individual began their reign as king of West Francia.
-
D.
reignAsCoRulerStart
chosen
Indicates the time or event when an entity begins to exercise ruling authority jointly with one or more other rulers.
-
E.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03faecd60819091eeaa56c9c8f67d |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:51 a.m.