Triple
T27290082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mufasa's pride |
E688596
|
entity |
| Predicate | royalLineageIncludes |
P57937
|
FINISHED |
| Object | Ahadi |
—
|
NE NERFINISHED |
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: Ahadi | Statement: [Mufasa's pride, royalLineageIncludes, Ahadi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalLineageIncludes Context triple: [Mufasa's pride, royalLineageIncludes, Ahadi]
-
A.
hasRoyalAncestryFrom
chosen
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
B.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
C.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
D.
parentOfRoyalDescendants
Indicates being the parent of one or more individuals who are of royal descent.
-
E.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 11:14 a.m.