Triple
T1272024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaza de Armas |
E15729
|
entity |
| Predicate | hasTouristInformation |
P7835
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Plaza de Armas, hasTouristInformation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristInformation Context triple: [Plaza de Armas, hasTouristInformation, yes]
-
A.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
B.
hasTouristInfrastructure
chosen
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
C.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
D.
touristGatewayTo
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
-
E.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c06c033081909bc594157abaf5bb |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.