Triple
T1458060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Australia |
E31443
|
entity |
| Predicate | seat |
P75
|
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: [High Court of Australia, seat, Canberra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Canberra Context triple: [High Court of Australia, seat, 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.
Adelaide
Adelaide is the coastal capital city of South Australia, known for its festivals, wine regions, and planned grid layout.
-
C.
Brisbane
Brisbane is the capital and most populous city of the Australian state of Queensland, known for its subtropical climate, riverfront setting, and role as a major economic and cultural hub.
-
D.
Melbourne
Melbourne is a major Australian city known for its vibrant arts scene, diverse culture, and status as a leading center for sports and education.
-
E.
Melbourne
Melbourne is a historic market town in Derbyshire, England, known for its Georgian architecture and the notable Melbourne Hall and gardens.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59a462881908e84b27846a6bc04 |
completed | March 1, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51a514908190b782eb1ca98d5b4c |
completed | March 8, 2026, 10:38 a.m. |
Created at: March 1, 2026, 8 p.m.