Triple
T15347859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshine Coast hinterland |
E366971
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Flaxton |
E1137180
|
NE 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: Flaxton | Statement: [Sunshine Coast hinterland, hasTown, Flaxton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flaxton Context triple: [Sunshine Coast hinterland, hasTown, Flaxton]
-
A.
Flaxton
Flaxton is a small village and civil parish in North Yorkshire, England, known for its rural character and agricultural surroundings.
-
B.
Flaxton
chosen
Flaxton is a small rural town in Queensland, Australia, situated in the scenic hinterland of the Sunshine Coast.
-
C.
Winlaton
Winlaton is a village in Tyne and Wear, England, historically associated with coal mining and early industrial development.
-
D.
Monkton
Monkton is a small village in South Ayrshire, Scotland, situated near Prestwick and close to the west coast.
-
E.
Linnton
Linnton is a riverside neighborhood in northwest Portland, Oregon, characterized by its mix of industrial areas, forested hillsides, and access to the Willamette River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01fb46b48190a030e40ee0163559 |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.