Triple
T883446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William the Conqueror |
E19075
|
entity |
| Predicate | reignAsKingOfEnglandEnd |
P10353
|
FINISHED |
| Object | 1087-09-09 |
—
|
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: 1087-09-09 | Statement: [William the Conqueror, reignAsKingOfEnglandEnd, 1087-09-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsKingOfEnglandEnd Context triple: [William the Conqueror, reignAsKingOfEnglandEnd, 1087-09-09]
-
A.
successorAsKingOfEngland
Indicates that one person becomes the next King of England following another person's reign.
-
B.
succeededByAsKingOfHanover
Indicates that one individual was directly followed by another as the reigning king of Hanover.
-
C.
reignAsQueenConsortOfEnglandEnd
Indicates the time or event at which an individual’s tenure as Queen Consort of England comes to an end.
-
D.
reignAs
chosen
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
E.
reignAsQueenConsortOfScotlandEnd
Indicates the time or event marking when an individual’s tenure as queen consort of Scotland comes to an end.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accda4148190aa628dab14d7f5de |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.