Triple
T6825849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de la Liberación |
E157012
|
entity |
| Predicate | hasNearbyCommercialActivity |
P71206
|
FINISHED |
| Object | restaurants |
—
|
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: restaurants | Statement: [Plaza de la Liberación, hasNearbyCommercialActivity, restaurants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCommercialActivity Context triple: [Plaza de la Liberación, hasNearbyCommercialActivity, restaurants]
-
A.
nearbyEconomicActivity
chosen
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
-
B.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
C.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
D.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
E.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d58375248190935dd38d618994e3 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.