Triple
T16687931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peel River |
E405513
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Nundle |
E909563
|
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: Nundle | Statement: [Peel River, hasNearbyTown, Nundle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nundle Context triple: [Peel River, hasNearbyTown, Nundle]
-
A.
Nundle
chosen
Nundle is a small historic village in the New England region of New South Wales, Australia, known for its gold rush heritage and rural charm.
-
B.
Tindal
Tindal is a surname and variant spelling of Tyndal, historically associated with English and Scottish families and occasionally used as a given name.
-
C.
Bournedale
Bournedale is a small village in the town of Bourne, Massachusetts, known for its rural character and proximity to the Cape Cod Canal.
-
D.
Nouster
Nouster is a small settlement on the Orkney island of North Ronaldsay in Scotland.
-
E.
Ridgmont
Ridgmont is a small village and civil parish in Bedfordshire, England, known for its rural character and proximity to the Woburn Estate.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea75df481909a7ebb9b2a9d0afd |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0091966fbc81908cd1db230ddbb82b |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.