Triple
T14620125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overland Track |
E343194
|
entity |
| Predicate | bookingSeason |
P98622
|
FINISHED |
| Object | 1 October to 31 May |
—
|
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: 1 October to 31 May | Statement: [Overland Track, bookingSeason, 1 October to 31 May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingSeason Context triple: [Overland Track, bookingSeason, 1 October to 31 May]
-
A.
peakSeasonMonth
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
-
B.
seasonMonths
chosen
Indicates the set of calendar months during which a given season occurs.
-
C.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
-
D.
navigationSeason
Indicates the time period or season during which navigation or travel along a route or waterway is possible or permitted.
-
E.
requiresReservationInPeakSeason
Indicates that the subject can only be accessed or used during peak season if a reservation has been made in advance.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46550e48190af45f426f02579bb |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.