Triple
T2506227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince William of Gloucester |
E52586
|
entity |
| Predicate | lineOfSuccessionPositionAtBirth |
P13159
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Prince William of Gloucester, lineOfSuccessionPositionAtBirth, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOfSuccessionPositionAtBirth Context triple: [Prince William of Gloucester, lineOfSuccessionPositionAtBirth, 4]
-
A.
positionInLineOfSuccessionAtBirth
chosen
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
B.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
C.
dateOfBirthOfChildRoyalReign
Indicates the specific date on which a child was born during a particular royal’s reign.
-
D.
successorAsPrincessRoyal
Indicates that one person becomes the next holder of the title "Princess Royal" after another person.
-
E.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.