Triple
T27678396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horseshoe Bay–Langdale route |
E697841
|
entity |
| Predicate | endPointArea |
P390
|
FINISHED |
| Object | Sunshine Coast Regional District |
—
|
NE NERFINISHED |
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: Sunshine Coast Regional District | Statement: [Horseshoe Bay–Langdale route, endPointArea, Sunshine Coast Regional District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endPointArea Context triple: [Horseshoe Bay–Langdale route, endPointArea, Sunshine Coast Regional District]
-
A.
typicalEndpointArea
Indicates that a location or region is the usual or characteristic area where an endpoint (such as a process, structure, or event outcome) occurs or is situated.
-
B.
areaBControl
Indicates that one entity has control or authority over a specific region or area labeled as B.
-
C.
hasAreaNumber
Indicates that an entity is associated with a specific area identified by a numerical code.
-
D.
venueArea
Indicates the physical size or spatial extent of a venue, typically measured in units such as square meters or square feet.
-
E.
endPoint
chosen
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:45 p.m.