Triple
T5385381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balkh |
E120189
|
entity |
| Predicate | cultureCenterOf |
P4313
|
FINISHED |
| Object | Persian culture |
—
|
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: Persian culture | Statement: [Balkh, cultureCenterOf, Persian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureCenterOf Context triple: [Balkh, cultureCenterOf, Persian culture]
-
A.
centerOfCult
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
-
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.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
D.
hasCulturalCentre
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
-
E.
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.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f5a7388190aa4ba2052afca74e |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.