Triple
T7018523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACT Legislative Assembly |
E162756
|
entity |
| Predicate | oversees |
P46
|
FINISHED |
| Object | ACT Government |
E177636
|
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: ACT Government | Statement: [ACT Legislative Assembly, oversees, ACT Government]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ACT Government Context triple: [ACT Legislative Assembly, oversees, ACT Government]
-
A.
ACT Government
chosen
The ACT Government is the administrative authority responsible for governing the Australian Capital Territory, including its public services, infrastructure, and environmental management.
-
B.
GOV
GOV is the National Rail station code used to identify Govan subway station in Glasgow, Scotland.
-
C.
Home Government Association
The Home Government Association was an early 19th-century Irish political organization that campaigned for domestic self-government and laid groundwork for the broader Irish Home Rule movement.
-
D.
ACT
ACT is the standard vehicle registration code used for the Australian Capital Territory in Australia.
-
E.
ACT
ACT is NATO’s strategic command responsible for leading the alliance’s military transformation, innovation, and future capability development.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1e79c108190a507335e9dbf2716 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7756a50608190b548ce4aeaaf9f9d |
completed | March 28, 2026, 6:30 a.m. |
Created at: March 27, 2026, 2:34 p.m.