Triple
T15321121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Jagungal |
E366291
|
entity |
| Predicate | nearestTown |
P350
|
FINISHED |
| Object | Adaminaby |
E366499
|
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: Adaminaby | Statement: [Mount Jagungal, nearestTown, Adaminaby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adaminaby Context triple: [Mount Jagungal, nearestTown, Adaminaby]
-
A.
Adaminaby
chosen
Adaminaby is a small town in New South Wales, Australia, known as a gateway to the Snowy Mountains and the Snowy Mountains Scheme.
-
B.
Keadby
Keadby is a village in North Lincolnshire, England, known for its location on the River Trent and its nearby power station and transport links.
-
C.
Lamorbey
Lamorbey is a suburban residential area in southeast London, known for its parks, historic buildings, and proximity to Sidcup within the London Borough of Bexley.
-
D.
Anlaby
Anlaby is a suburban village in the East Riding of Yorkshire, England, situated just west of Kingston upon Hull.
-
E.
Nesseby
Nesseby is a small coastal municipality in Troms og Finnmark county in northern Norway, known for its Sámi culture and location along the Varangerfjorden.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd460288190b5c41f0a0aeee949 |
completed | April 16, 2026, 1:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8a9085881909904152c32b0fed1 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.