Triple
T6183697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Minister of State |
E138003
|
entity |
| Predicate | powerBasedOn |
P14894
|
FINISHED |
| Object | royal confidence |
—
|
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 confidence | Statement: [First Minister of State, powerBasedOn, royal confidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerBasedOn Context triple: [First Minister of State, powerBasedOn, royal confidence]
-
A.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
B.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
C.
powerDependsOn
chosen
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
D.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
E.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06100c2b0819097f287e86f63d590 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.