Triple
T7014613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub‑Committee on Administrative, Budgetary and Financial Matters |
E162667
|
entity |
| Predicate | decisionLevel |
P27741
|
FINISHED |
| Object | preparatory |
—
|
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: preparatory | Statement: [Sub‑Committee on Administrative, Budgetary and Financial Matters, decisionLevel, preparatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionLevel Context triple: [Sub‑Committee on Administrative, Budgetary and Financial Matters, decisionLevel, preparatory]
-
A.
decisionMakingLevel
chosen
Indicates the degree or hierarchy of authority an entity has in making decisions within a given context.
-
B.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
C.
decisionScope
Indicates the range or domain within which a particular decision is valid, applicable, or has authority.
-
D.
decisionFrequency
Indicates how often decisions are made or actions are chosen within a given process or interaction.
-
E.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.