Triple
T154896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State (Portugal) |
E3157
|
entity |
| Predicate | bindingForceOfOpinions |
P1045
|
FINISHED |
| Object | non-binding |
—
|
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: non-binding | Statement: [Council of State (Portugal), bindingForceOfOpinions, non-binding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingForceOfOpinions Context triple: [Council of State (Portugal), bindingForceOfOpinions, non-binding]
-
A.
opinionBy
Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
-
B.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
C.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
D.
bindingOn
chosen
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
E.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2565c727c8190bca9ba6ca52f216a |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.