Triple
T12474628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASA |
E298143
|
entity |
| Predicate | headquartersLocation |
P62
|
FINISHED |
| Object | Canberra |
E15148
|
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: Canberra | Statement: [CASA, headquartersLocation, Canberra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Canberra Context triple: [CASA, headquartersLocation, Canberra]
-
A.
Canberra
chosen
Canberra is the planned capital city of Australia, known for its national government institutions, cultural landmarks, and garden-city design.
-
B.
Civic, Canberra
Civic, Canberra is the central business district and main commercial and cultural hub of Australia's capital city, Canberra.
-
C.
Pialligo, Canberra
Pialligo, Canberra is a semi-rural suburb on the eastern edge of Australia's capital known for its orchards, plant nurseries, and proximity to Canberra Airport.
-
D.
Queanbeyan
Queanbeyan is a regional city in southeastern New South Wales, Australia, located just outside Canberra and functioning as a residential and commercial hub for the surrounding area.
-
E.
Adelaide
Adelaide is the coastal capital city of South Australia, known for its festivals, wine regions, and planned grid layout.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dcb194c81908b5e0320ddfd463c |
completed | April 10, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f002b7c81909ee9d4ea3ea6d5f2 |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:56 p.m.