Triple
T22466074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Block courtyard chamber |
E555356
|
entity |
| Predicate | openedForParliamentaryUse |
P101547
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [West Block courtyard chamber, openedForParliamentaryUse, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForParliamentaryUse Context triple: [West Block courtyard chamber, openedForParliamentaryUse, 2019]
-
A.
usedInParliament
Indicates that something (such as a procedure, term, rule, or item) is employed or applied within the context of a parliamentary body or its activities.
-
B.
usesParliament
Indicates that one entity conducts its legislative or decision‑making processes through a parliamentary body or system.
-
C.
openedForUseBy
Indicates that something has been made available or activated so that a particular entity can use it.
-
D.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
-
E.
establishedForParliament
chosen
Indicates that something (such as an institution, body, or arrangement) was created or set up specifically for the use, function, or purposes of a parliament.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b837ec081909c4e44d37e8b2acd |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.