Triple
T744116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian monarchy |
E15303
|
entity |
| Predicate | parliamentarySystem |
P15721
|
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: [Belgian monarchy, parliamentarySystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentarySystem Context triple: [Belgian monarchy, parliamentarySystem, yes]
-
A.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
-
B.
parliamentaryContext
Indicates that an action, statement, or event occurs within, relates to, or is governed by the procedures and norms of a parliamentary setting or legislative body.
-
C.
politicalForm
chosen
Indicates the type or structure of governance or political organization that characterizes an entity.
-
D.
parliamentaryGroupType
Indicates the specific kind or category of parliamentary group to which an entity belongs.
-
E.
parliamentaryGroup
Indicates that an entity is a parliamentary group (or caucus) with which another political actor, such as a legislator or party, is affiliated or associated.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a610ba9881908b4e5e7dcc6ed0f5 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.