Triple
T14365909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mittagong |
E356232
|
entity |
| Predicate | nearbyTown |
P3883
|
FINISHED |
| Object | Berrima |
E359905
|
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: Berrima | Statement: [Mittagong, nearbyTown, Berrima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berrima Context triple: [Mittagong, nearbyTown, Berrima]
-
A.
Berrima
chosen
Berrima is a historic village in New South Wales, Australia, known for its well-preserved colonial architecture and heritage-listed buildings.
-
B.
Mullumbimby
Mullumbimby is a small town in northern New South Wales, Australia, known for its alternative culture and proximity to the Byron Bay region.
-
C.
Boorowa
Boorowa is a rural town in New South Wales, Australia, known for its rich agricultural surroundings and heritage streetscapes.
-
D.
Wamberal
Wamberal is a coastal suburb on the Central Coast of New South Wales, Australia, known for its long sandy beach and residential lifestyle.
-
E.
Murrumbucca
Murrumbucca is a rural locality in the Snowy Monaro region of New South Wales, Australia.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fad48748190a0f34ca4d02f9a3c |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd1bb1c48190b5d2b4167c756abf |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 1:15 a.m.