Triple
T35308583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophet Muhammad through Fatimah |
E1019704
|
entity |
| Predicate | includesLineageOf |
P77522
|
FINISHED |
| Object | Hasan ibn Ali |
E78676
|
NE 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: Hasan ibn Ali | Statement: [Prophet Muhammad through Fatimah, includesLineageOf, Hasan ibn Ali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLineageOf Context triple: [Prophet Muhammad through Fatimah, includesLineageOf, Hasan ibn Ali]
-
A.
containsLineages
Indicates that one entity includes or encompasses one or more specified lineages within its scope or structure.
-
B.
impliesLineage
Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
-
C.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
D.
hasLineageCharacteristic
Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
-
E.
hasLineageMember
chosen
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
- F. None of above.
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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382ca916188190a3be22c746ec76b2 |
completed | June 21, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.