Triple
T35119198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Council |
E1014120
|
entity |
| Predicate | decisionsRequire |
P15229
|
FINISHED |
| Object | royal approval |
—
|
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: royal approval | Statement: [Small Council, decisionsRequire, royal approval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionsRequire Context triple: [Small Council, decisionsRequire, royal approval]
-
A.
requiresDecision
Indicates that a choice or judgment must be made regarding the associated entities or situation.
-
B.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
C.
includesDecisionsBy
Indicates that something contains, encompasses, or takes into account decisions made by a specified party or set of parties.
-
D.
decisionsSubjectTo
chosen
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
-
E.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.