Triple
T24368037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exmouth |
E614252
|
entity |
| Predicate | drivingTimeFromPerth |
P155944
|
FINISHED |
| Object | about 12–13 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: about 12–13 hours | Statement: [Exmouth, drivingTimeFromPerth, about 12–13 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingTimeFromPerth Context triple: [Exmouth, drivingTimeFromPerth, about 12–13 hours]
-
A.
distanceToPerth
Indicates the measured distance between a given entity’s location and the city of Perth.
-
B.
drivingTimeFromSydney
Indicates the amount of time it takes to drive from Sydney to a specified location.
-
C.
approxDrivingTimeFromMelbourne
Indicates the estimated duration it takes to drive from Melbourne to a specified location.
-
D.
typicalJourneyTimeAdelaideDarwin
Indicates the usual or average amount of time it takes to travel from Adelaide to Darwin.
-
E.
approximateDrivingTimeFromBrisbane
Indicates the estimated amount of time it takes to drive from Brisbane to a specified location.
- F. None of above. chosen
Provenance (4 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29388c9308190a7a70bf75ed1501c |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:01 a.m.