Triple
T20934717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Premium |
E515552
|
entity |
| Predicate | usedToEvaluate |
P77543
|
FINISHED |
| Object | feasibility of climate policies |
—
|
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: feasibility of climate policies | Statement: [Green Premium, usedToEvaluate, feasibility of climate policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToEvaluate Context triple: [Green Premium, usedToEvaluate, feasibility of climate policies]
-
A.
evaluationUse
chosen
Indicates that something is used as a basis, tool, or resource for evaluating or assessing something else.
-
B.
isUsedToCompute
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
C.
usedToSelect
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining another entity.
-
D.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
E.
usedToHandle
Indicates that one entity previously managed, processed, or dealt with another entity as part of its function or role.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f950d5e081908ec0df4824cf69f7 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.