Triple
T15102385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coomera |
E360699
|
entity |
| Predicate | hasNearbySuburb |
P41355
|
FINISHED |
| Object | Oxenford |
E346483
|
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: Oxenford | Statement: [Coomera, hasNearbySuburb, Oxenford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oxenford Context triple: [Coomera, hasNearbySuburb, Oxenford]
-
A.
Oxenford
chosen
Oxenford is a suburb on the Gold Coast in Queensland, Australia, known for its major theme parks and family-oriented attractions.
-
B.
Wangford
Wangford is a small rural village and civil parish located in the English county of Suffolk.
-
C.
Broadford
Broadford is a village on the Isle of Skye in Scotland’s Inner Hebrides, known as one of the island’s main population centers and a base for exploring the surrounding landscapes.
-
D.
Mordiford
Mordiford is a small village in Herefordshire, England, known for its picturesque rural setting near the confluence of the Rivers Lugg and Wye and its associated local legends.
-
E.
Yoxford
Yoxford is a small rural village in eastern England known for its historic buildings and location near the Suffolk coast.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00551521c8190b48d1a074bb4bdfc |
completed | April 15, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae2571f48190b73f0aecd113fed6 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:05 a.m.