Triple
T8307778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaʿfar ibn Abi Talib |
E194505
|
entity |
| Predicate | roleInAbyssinia |
P82661
|
FINISHED |
| Object | Leader of Muslim emigrants |
—
|
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: Leader of Muslim emigrants | Statement: [Jaʿfar ibn Abi Talib, roleInAbyssinia, Leader of Muslim emigrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAbyssinia Context triple: [Jaʿfar ibn Abi Talib, roleInAbyssinia, Leader of Muslim emigrants]
-
A.
EgyptRole
Indicates that an entity holds a specific role, function, or capacity in relation to Egypt.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
roleInArabia
Indicates that an entity holds or held a specific role, position, or function within the context of Arabia.
-
D.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
E.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2a86bc81909749c40c640aa9f8 |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:54 p.m.