Triple
T4315016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mansur |
E94166
|
entity |
| Predicate | madeBaghdadCulturalCenterOf |
P4313
|
FINISHED |
| Object | Islamic world |
—
|
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: Islamic world | Statement: [Al-Mansur, madeBaghdadCulturalCenterOf, Islamic world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeBaghdadCulturalCenterOf Context triple: [Al-Mansur, madeBaghdadCulturalCenterOf, Islamic world]
-
A.
hasIslamicCenter
Indicates that a place or entity possesses, hosts, or contains an Islamic center as part of its facilities or within its boundaries.
-
B.
isCulturalCenterFor
chosen
Indicates that one entity serves as a primary hub or focal point for the cultural activities, heritage, or identity of another entity.
-
C.
isCulturalCenter
Indicates that an entity serves as a primary hub or focal point for the cultural activities, expressions, and institutions of a community or region.
-
D.
hasCulturalCentre
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
-
E.
distanceFromBaghdad
Indicates the spatial distance between a given location or entity and the city of Baghdad.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350f4448481908be2c7df9cc71bb9 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.