Triple
T1478800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Royal |
E30902
|
entity |
| Predicate | heldByPrincessLouiseDaughterOfEdwardVII |
P29227
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Princess Royal, heldByPrincessLouiseDaughterOfEdwardVII, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByPrincessLouiseDaughterOfEdwardVII Context triple: [Princess Royal, heldByPrincessLouiseDaughterOfEdwardVII, true]
-
A.
holderPrincessMayOfTeckSpouse
Indicates that the holder has Princess May of Teck as their spouse.
-
B.
dateBecamePrincessRoyal
Indicates the specific date on which an individual assumed the title or status of Princess Royal.
-
C.
successorAsPrincessRoyal
Indicates that one person becomes the next holder of the title "Princess Royal" after another person.
-
D.
reignAsQueenConsortOfEnglandEnd
Indicates the time or event at which an individual’s tenure as Queen Consort of England comes to an end.
-
E.
founderOfHouseOfWindsor
Indicates that a person is the one who established or originated the House of Windsor as a royal dynasty.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6739d2481909ea8d8e075f62cf3 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c57984088190b2c2d2d9cc2e5df9 |
completed | March 1, 2026, 11:02 p.m. |
Created at: March 1, 2026, 8:11 p.m.