Triple
T8850975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhul-Kifl |
E210635
|
entity |
| Predicate | hasExpandedNarrativesIn |
P84989
|
FINISHED |
| Object | later Islamic tradition |
—
|
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: later Islamic tradition | Statement: [Dhul-Kifl, hasExpandedNarrativesIn, later Islamic tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpandedNarrativesIn Context triple: [Dhul-Kifl, hasExpandedNarrativesIn, later Islamic tradition]
-
A.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
B.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
C.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
D.
wasExpanded
Indicates that something increased in size, scope, or extent compared to its previous state.
-
E.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c2300c819097b1ca6ebe2f749a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:49 p.m.