Triple
T22641783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urunga Boardwalk |
E558847
|
entity |
| Predicate | town |
P3385
|
FINISHED |
| Object | Urunga |
E129685
|
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: Urunga | Statement: [Urunga Boardwalk, town, Urunga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Urunga Context triple: [Urunga Boardwalk, town, Urunga]
-
A.
Urunga
chosen
Urunga is a small coastal town in New South Wales, Australia, known for its scenic boardwalks, estuary views, and relaxed seaside atmosphere.
-
B.
Ulihatu
Ulihatu is a village in Jharkhand, India, best known as the birthplace of tribal freedom fighter Birsa Munda.
-
C.
Gundunguri
Gundunguri is an alternative name for the Gundungurra, an Aboriginal Australian people traditionally associated with the Southern Highlands and Blue Mountains region of New South Wales.
-
D.
Urakhi
Urakhi is a dialect of the Dargin language spoken by a subset of the Dargin people in the North Caucasus region of Russia.
-
E.
Karanga
Karanga is a major dialect of the Shona language spoken primarily in southern Zimbabwe, known for its distinct phonological and lexical features.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703489a48190bd97a7eb7a571b64 |
completed | April 29, 2026, 2:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b5860a6c88190b01cfc31d2e839ac |
completed | May 18, 2026, 6:20 p.m. |
Created at: April 17, 2026, 3:04 p.m.