Triple
T27010399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Tolima |
E680367
|
entity |
| Predicate | hasCulturalHub |
P2412
|
FINISHED |
| Object | Chaparral |
—
|
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: Chaparral | Statement: [Southern Tolima, hasCulturalHub, Chaparral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalHub Context triple: [Southern Tolima, hasCulturalHub, Chaparral]
-
A.
hasCulturalCentre
chosen
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
-
B.
hasCulturalCenterFunction
Indicates that something serves the role or performs the activities of a cultural center, such as hosting cultural events, programs, or services.
-
C.
hasCulturalOrganization
Indicates that an entity possesses, is associated with, or hosts a cultural organization (such as a museum, arts group, or cultural institution).
-
D.
hasCulturalCommunity
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
-
E.
hasCulturalAttractions
Indicates that a place or entity possesses notable cultural points of interest, such as museums, theaters, historic sites, or artistic venues.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 7:02 a.m.