Triple
T35883336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalila wa Dimna |
E1037570
|
entity |
| Predicate | placeOfArabicAdaptation |
P88505
|
FINISHED |
| Object | Abbasid Caliphate |
—
|
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: Abbasid Caliphate | Statement: [Kalila wa Dimna, placeOfArabicAdaptation, Abbasid Caliphate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfArabicAdaptation Context triple: [Kalila wa Dimna, placeOfArabicAdaptation, Abbasid Caliphate]
-
A.
hasArabPopulation
Indicates that an entity possesses or includes a population composed of Arab people.
-
B.
hasArabComponent
Indicates that something includes or contains an Arab-related part, element, or component as one of its constituents.
-
C.
regionAllocatedToArabState
Indicates that a particular geographic region has been designated or assigned to be part of an Arab state.
-
D.
correspondsToInArabic
Indicates that one entity is the equivalent or matching counterpart of another entity specifically in the Arabic language.
-
E.
tookPlaceInCaliphate
chosen
Indicates that an event or action occurred within the territorial or political domain of a caliphate.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:06 p.m.