Triple
T20600370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkes Way |
E506160
|
entity |
| Predicate | maintainedBy |
P86
|
FINISHED |
| Object | ACT Government |
—
|
NE NERFINISHED |
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: [Parkes Way, maintainedBy, ACT Government]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ACT Government Context triple: [Parkes Way, maintainedBy, 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 IATA airport code for Gove Airport, a regional airport serving the Gove Peninsula in the Northern Territory of Australia.
-
C.
GOV
GOV is the National Rail station code used to identify Govan subway station in Glasgow, Scotland.
-
D.
GOV
GOV is an honorific suffix used in the United Kingdom to denote a Governor, particularly in formal titles such as that of a central bank governor.
-
E.
BGOV
BGOV is Bloomberg Government’s specialized platform providing data-driven news, analysis, and tools focused on U.S. federal policy, legislation, and government contracting.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1ef9ac8190b05e23c149529cb9 |
completed | April 20, 2026, 10:35 p.m. |
Created at: April 16, 2026, 11:41 a.m.