Triple
T15520866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarch of Barbados |
E368961
|
entity |
| Predicate | powersType |
P118971
|
FINISHED |
| Object | reserve powers |
—
|
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: reserve powers | Statement: [Monarch of Barbados, powersType, reserve powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powersType Context triple: [Monarch of Barbados, powersType, reserve powers]
-
A.
powersFeature
Indicates that one entity provides the underlying functionality or capability that enables a particular feature of another entity.
-
B.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
C.
powerDependsOn
Indicates that the power or effectiveness of one entity is contingent upon, or influenced by, another entity.
-
D.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
E.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
- F. None of above. chosen
Provenance (4 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0403543188190abac49d2b9decb89 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:04 a.m.