Triple
T743736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Belgium |
E15296
|
entity |
| Predicate | definesBranch |
P18917
|
FINISHED |
| Object | legislative power |
—
|
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: legislative power | Statement: [Constitution of Belgium, definesBranch, legislative power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesBranch Context triple: [Constitution of Belgium, definesBranch, legislative power]
-
A.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
B.
branchPosition
Indicates the relative location or placement of something along a branch.
-
C.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
D.
isUniqueBranchOf
Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
-
E.
branchingPattern
Indicates the structural way in which one element divides into multiple offshoots or subdivisions from a common source.
- 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_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_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5a35c68819082429755c046e9a7 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.