Triple
T36430383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calle 60 |
E897424
|
entity |
| Predicate | isCulturalAxisOf |
P160783
|
FINISHED |
| Object | Mérida |
—
|
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: Mérida | Statement: [Calle 60, isCulturalAxisOf, Mérida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCulturalAxisOf Context triple: [Calle 60, isCulturalAxisOf, Mérida]
-
A.
isCulturalCorridorIn
Indicates that a designated cultural corridor is located within or belongs to a specified geographic or administrative area.
-
B.
hasCulturalRelation
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
C.
countryOfCulturalSignificance
Indicates that a country holds notable cultural importance or influence for a given entity, such as a person, group, object, or practice.
-
D.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
-
E.
isCulturalAreaFor
chosen
Indicates that one entity serves as a designated cultural area or space intended for the cultural activities, practices, or identity of another entity.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.