Triple
T3052221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the House |
E60395
|
entity |
| Predicate | hasHansardRecord |
P45369
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [the House, hasHansardRecord, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHansardRecord Context triple: [the House, hasHansardRecord, yes]
-
A.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
containsParliament
Indicates that one political or administrative entity includes a parliament within its structure or jurisdiction.
-
C.
hasGeneralAssembly
Indicates that an entity possesses or is associated with a general assembly as its formal deliberative or decision-making body.
-
D.
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.
-
E.
hasParliamentMembers
Indicates that a governing body or political entity possesses or is represented by one or more members in a parliament.
- F. None of above. chosen
Provenance (4 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf274f88190a759f9ce3da47c35 |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad9b272a408190ba0ce09bdeea76c9 |
completed | March 8, 2026, 3:52 p.m. |
Created at: March 8, 2026, 3:01 p.m.