Triple
T291901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James II of England |
E6011
|
entity |
| Predicate | reignStartAsKingOfEngland |
P1506
|
FINISHED |
| Object | 1685-02-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: 1685-02-06 | Statement: [James II of England, reignStartAsKingOfEngland, 1685-02-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsKingOfEngland Context triple: [James II of England, reignStartAsKingOfEngland, 1685-02-06]
-
A.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
C.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
D.
succeededByAsKingOfHanover
Indicates that one individual was directly followed by another as the reigning king of Hanover.
-
E.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.