Triple
T26876835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Hashemi |
E676774
|
entity |
| Predicate | associatedAncestor |
P89662
|
FINISHED |
| Object | Hashim ibn Abd Manaf |
—
|
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: Hashim ibn Abd Manaf | Statement: [Al-Hashemi, associatedAncestor, Hashim ibn Abd Manaf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAncestor Context triple: [Al-Hashemi, associatedAncestor, Hashim ibn Abd Manaf]
-
A.
associatedWithDescendants
Indicates that an entity has a relationship or connection specifically involving the descendants of another entity.
-
B.
relationToAncestors
chosen
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
C.
proposesAncestor
Indicates that one entity puts forward or suggests another entity as a possible ancestor in a lineage or hierarchy.
-
D.
associatedBase
Indicates a relationship where one entity is linked or connected to a corresponding base entity that it depends on or is derived from.
-
E.
destinedAncestorOf
Indicates that one entity is fated or preordained to become an ancestor of another entity in the future.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: April 27, 2026, 5:36 a.m.