Triple
T16468944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodora Porphyrogenita |
E400008
|
entity |
| Predicate | coReignStart |
P31122
|
FINISHED |
| Object | 19 April 1042 |
—
|
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: 19 April 1042 | Statement: [Theodora Porphyrogenita, coReignStart, 19 April 1042]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coReignStart Context triple: [Theodora Porphyrogenita, coReignStart, 19 April 1042]
-
A.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
-
C.
reignClaimStart
Indicates the point in time when a person’s asserted or contested rule or reign is claimed to have begun.
-
D.
duchyReignStart
Indicates the point in time when an entity begins its rule or governance over a duchy.
-
E.
coRegencyStart
chosen
Indicates the point in time when a joint rule or shared reign between two or more authorities begins.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dce342081909cad56dc92de13a2 |
completed | April 18, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.