Triple
T14620126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overland Track |
E343194
|
entity |
| Predicate | directionRequirementInMainSeason |
P13659
|
FINISHED |
| Object | north to south |
—
|
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: north to south | Statement: [Overland Track, directionRequirementInMainSeason, north to south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionRequirementInMainSeason Context triple: [Overland Track, directionRequirementInMainSeason, north to south]
-
A.
directionFromMainLands
Indicates the cardinal or relative direction in which something is located or extends from the main lands.
-
B.
navigationSeason
Indicates the time period or season during which navigation or travel along a route or waterway is possible or permitted.
-
C.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
D.
navigationSeasonInfluencedBy
Indicates that the conditions or characteristics of a navigation season are affected or determined by another factor or entity.
-
E.
primaryDirection
chosen
Indicates the main or dominant directional orientation associated with an entity or relation.
- 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.