Triple
T429925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castillo San Cristóbal |
E9689
|
entity |
| Predicate | visitorActivities |
P5308
|
FINISHED |
| Object | guided tours |
—
|
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: guided tours | Statement: [Castillo San Cristóbal, visitorActivities, guided tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorActivities Context triple: [Castillo San Cristóbal, visitorActivities, guided tours]
-
A.
visitorCount
Indicates the number of visitors associated with a particular entity, context, or time period.
-
B.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
C.
notableVisit
Indicates that one entity made a visit to another entity or location that is considered significant or noteworthy.
-
D.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
E.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeedf68c81908473d6c6600961bd |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.