Triple
T10274576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idris II |
E240928
|
entity |
| Predicate | succeededAsChild |
P93064
|
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: [Idris II, succeededAsChild, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAsChild Context triple: [Idris II, succeededAsChild, true]
-
A.
succeededMother
Indicates that one entity has taken over or followed in the role, position, or status previously held by its mother.
-
B.
successorChild
Indicates that one entity is the child of another entity who is its immediate predecessor or predecessor in a succession or lineage.
-
C.
capturedAsChild
Indicates that one entity was taken into custody, control, or confinement by another entity while still a child.
-
D.
succeededByName
Indicates that one entity is followed or replaced by another entity identified by a specific name.
-
E.
succeededAsHeir
Indicates that one entity became the heir in place of, or following, another entity, typically upon the latter’s death or abdication.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d28a9c508190824867c04e8dcbe7 |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d285812c8190ab910dc85c53eebf |
completed | April 7, 2026, 9:46 a.m. |
Created at: April 6, 2026, 11:36 a.m.