Triple
T33859270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King-in-Council (federal Cabinet) |
E867876
|
entity |
| Predicate | membersTypicallyAre |
P2776
|
FINISHED |
| Object | members of Parliament |
—
|
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: members of Parliament | Statement: [King-in-Council (federal Cabinet), membersTypicallyAre, members of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersTypicallyAre Context triple: [King-in-Council (federal Cabinet), membersTypicallyAre, members of Parliament]
-
A.
typicalMembers
chosen
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
B.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
C.
membershipPropertiesAre
Indicates that specific properties or attributes are associated with, or required for, a particular membership.
-
D.
membersAreRegardedAs
Indicates that certain individuals or entities are viewed or treated as members of a particular group or organization.
-
E.
membersServe
Indicates that the members of a group perform services or duties for, or on behalf of, another entity or organization.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:47 a.m.