Triple
T3928499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Antonio River Walk |
E93335
|
entity |
| Predicate | touristCount |
P427
|
FINISHED |
| Object | millions of visitors per year |
—
|
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: millions of visitors per year | Statement: [San Antonio River Walk, touristCount, millions of visitors per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristCount Context triple: [San Antonio River Walk, touristCount, millions of visitors per year]
-
A.
touristArrivalsShareInTerritory
Indicates the proportion of total tourist arrivals that occur within a specific territory relative to a larger reference area or total.
-
B.
touristArrivalsPerYearApprox
Indicates an approximate count of how many tourists arrive at a place over the course of a year.
-
C.
visitorCount
chosen
Indicates the number of visitors associated with a particular entity, context, or time period.
-
D.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
E.
hasTouristPopularity
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeda65b708190b24cd715915aec1d |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.