Triple
T1234550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raíces Fountain |
E26516
|
entity |
| Predicate | touristSignificance |
P7889
|
FINISHED |
| Object | iconic landmark of Old San Juan |
—
|
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: iconic landmark of Old San Juan | Statement: [Raíces Fountain, touristSignificance, iconic landmark of Old San Juan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristSignificance Context triple: [Raíces Fountain, touristSignificance, iconic landmark of Old San Juan]
-
A.
tourismImportance
chosen
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
-
B.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
C.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
D.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5e421081908f2432528019db25 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.