Triple
T21420861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Sugar Cane Railway |
E528432
|
entity |
| Predicate | touristFocus |
P27612
|
FINISHED |
| Object | local history |
—
|
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: local history | Statement: [Australian Sugar Cane Railway, touristFocus, local history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristFocus Context triple: [Australian Sugar Cane Railway, touristFocus, local history]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismTheme
chosen
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
C.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
D.
tourismTrend
Indicates how patterns or levels of tourism activity change over time or across locations.
-
E.
primaryTourismHub
Indicates that a location serves as the main center or focal point for tourism activities within a given area or region.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d392e08190b7f378005afc9026 |
completed | April 26, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.