Triple
T27654692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nine Mile |
E696959
|
entity |
| Predicate | touristVisitorsFrom |
P75569
|
FINISHED |
| Object | international tourists |
—
|
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: international tourists | Statement: [Nine Mile, touristVisitorsFrom, international tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristVisitorsFrom Context triple: [Nine Mile, touristVisitorsFrom, international tourists]
-
A.
hasVisitorsFrom
chosen
Indicates that an entity receives or has received visitors originating from another specified entity or location.
-
B.
touristArrivalsPerYearApprox
Indicates an approximate count of how many tourists arrive at a place over the course of a year.
-
C.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
D.
touristArrivalsShareInTerritory
Indicates the proportion of total tourist arrivals that occur within a specific territory relative to a larger reference area or total.
-
E.
typicalVisitorsPerSeason
Indicates the usual number of visitors associated with each season for a given entity or location.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:33 p.m.