Triple
T33409369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imyremeshaw |
E855531
|
entity |
| Predicate | successorIsUncertain |
P200548
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Imyremeshaw, successorIsUncertain, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorIsUncertain Context triple: [Imyremeshaw, successorIsUncertain, true]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorFormation
Indicates that one entity comes into existence as the direct replacement or continuation of another, typically following the end or transformation of the predecessor.
-
C.
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.
-
D.
successorTitlePossible
Indicates that a particular title is eligible or allowed to be used as the successor to another title.
-
E.
successorClaimant
Indicates that one entity is the next or replacement claimant to a right, title, or claim previously held by another entity.
- F. None of above. chosen
Provenance (4 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
| PDg | Predicate description generation | batch_69ff956cd640819081efc31f313690b0 |
completed | May 9, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:36 a.m.