Triple
T9932584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advisory Committees |
E192680
|
entity |
| Predicate | advisoryPower |
P87814
|
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: [Advisory Committees, advisoryPower, non-binding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advisoryPower Context triple: [Advisory Committees, advisoryPower, non-binding]
-
A.
keyPowerAdvisedOn
Indicates that one entity provided guidance or recommendations to another entity regarding key power-related matters or decisions.
-
B.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
C.
exercisesPowersOnAdviceOf
chosen
Indicates that one entity exercises its formal powers or authority based on the advice or recommendations provided by another entity.
-
D.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
-
E.
assertedPower
Indicates that one entity has claimed, declared, or exercised authority, control, or dominance over another entity or domain.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b7897081909b28189aa57af250 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.