Triple
T3880871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GG |
E92816
|
entity |
| Predicate | successorDesignation |
P7979
|
FINISHED |
| Object | G |
—
|
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: G | Statement: [GG, successorDesignation, G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDesignation Context triple: [GG, successorDesignation, G]
-
A.
successorDesignationFor
Indicates the designation or identification of an entity that is intended to succeed or replace another entity in a given role, position, or function.
-
B.
successorDesignated
chosen
Indicates that one entity has been formally chosen or named to take over the role, position, or responsibilities of another entity in the future.
-
C.
successionRole
Indicates a role or position that one entity assumes as the successor to another in a sequence of holders or office-bearers.
-
D.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
E.
deFactoSuccessor
Indicates that one entity has effectively taken over the role, function, or position of another, even if not formally or legally recognized as its successor.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.