Triple
T20598170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Buller ski resort |
E506104
|
entity |
| Predicate | travelTimeFromMelbourneByCar |
P61012
|
FINISHED |
| Object | approximately 3 hours |
—
|
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: approximately 3 hours | Statement: [Mount Buller ski resort, travelTimeFromMelbourneByCar, approximately 3 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeFromMelbourneByCar Context triple: [Mount Buller ski resort, travelTimeFromMelbourneByCar, approximately 3 hours]
-
A.
approxDrivingTimeFromMelbourne
chosen
Indicates the estimated duration it takes to drive from Melbourne to a specified location.
-
B.
drivingTimeFromSydney
Indicates the amount of time it takes to drive from Sydney to a specified location.
-
C.
approximateDrivingTimeFromBrisbane
Indicates the estimated amount of time it takes to drive from Brisbane to a specified location.
-
D.
distanceToMelbourne
Indicates the spatial distance between a given location or entity and the city of Melbourne.
-
E.
typicalJourneyTimeAdelaideDarwin
Indicates the usual or average amount of time it takes to travel from Adelaide to Darwin.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1d15b08190a720fc7cefbf333e |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.