Triple
T5505136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Clarence and Avondale |
E144419
|
entity |
| Predicate | oneTimeSecondInLineTo |
P63341
|
FINISHED |
| Object | British throne |
—
|
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: British throne | Statement: [Duke of Clarence and Avondale, oneTimeSecondInLineTo, British throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneTimeSecondInLineTo Context triple: [Duke of Clarence and Avondale, oneTimeSecondInLineTo, British throne]
-
A.
secondInLine
chosen
Indicates that one entity occupies the second position in a sequence or queue immediately following the first.
-
B.
secondOnlyTo
Indicates that one entity ranks immediately below another in degree, importance, or quality, with only that other entity surpassing it.
-
C.
isNextInLineTo
Indicates that one entity is immediately scheduled or positioned to receive something or assume a role after another entity.
-
D.
operatesOnLine
Indicates that an entity conducts operations, services, or activities along a specific line or route.
-
E.
servesLineSince
Indicates that a transportation service or route has been operating on a particular line since a specified point in time.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0e91d08190a4db907030955bb3 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.