Triple
T999826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British royal family |
E21577
|
entity |
| Predicate | establishedAsHouseOfWindsorInYear |
P14035
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [British royal family, establishedAsHouseOfWindsorInYear, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsHouseOfWindsorInYear Context triple: [British royal family, establishedAsHouseOfWindsorInYear, 1917]
-
A.
royalDesignationYear
chosen
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
B.
reignAsKingOfEnglandStart
Indicates the time at which a person begins their reign as King of England.
-
C.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
D.
reignAsQueenConsortOfEnglandStart
Indicates the time at which an individual began serving as queen consort of England to a reigning English monarch.
-
E.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e3d8b081908e536928e7d6199d |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.