Triple
T2624982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Parliament House, Canberra |
E59095
|
entity |
| Predicate | functionStart |
P5925
|
FINISHED |
| Object | seat of the Parliament of Australia |
—
|
LITERAL 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: seat of the Parliament of Australia | Statement: [Old Parliament House, Canberra, functionStart, seat of the Parliament of Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionStart Context triple: [Old Parliament House, Canberra, functionStart, seat of the Parliament of Australia]
-
A.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
B.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
C.
instructionBegan
Indicates that an instructional process or teaching activity has started.
-
D.
formerFunction
chosen
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
openingFunction
Indicates that one entity serves as the initial or primary function, role, or operation that begins or initiates a process, sequence, or interaction involving another entity.
- F. None of above.
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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.