Triple
T171663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary of Teck |
E3489
|
entity |
| Predicate | reignAsQueenConsortStart |
P1506
|
FINISHED |
| Object | 1910-05-06 |
—
|
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: 1910-05-06 | Statement: [Mary of Teck, reignAsQueenConsortStart, 1910-05-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsQueenConsortStart Context triple: [Mary of Teck, reignAsQueenConsortStart, 1910-05-06]
-
A.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
C.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
D.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
E.
heirApparentDuringReign
Indicates that one entity was officially recognized as the designated heir apparent to another entity’s position or title during the latter’s period of reign.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25a3f9d188190aacf5791273e2c65 |
completed | Feb. 28, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69a25667717c8190bac5108366e2178d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.