Triple
T22133631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ii |
E546968
|
entity |
| Predicate | climateActionReputation |
P34811
|
FINISHED |
| Object | strong environmental initiatives |
—
|
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: strong environmental initiatives | Statement: [Ii, climateActionReputation, strong environmental initiatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateActionReputation Context triple: [Ii, climateActionReputation, strong environmental initiatives]
-
A.
environmentalReputation
chosen
Indicates the perceived quality or standing of an entity’s environmental practices, impact, or responsibility.
-
B.
sustainabilityRating
Indicates the assessed level of how environmentally and socially sustainable an entity, product, or activity is.
-
C.
crowdReputation
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
D.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
E.
issuerESGFocus
Indicates that the issuer emphasizes or prioritizes environmental, social, and governance (ESG) factors in its activities or strategy.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b81d5c819085fd18bf3ae28333 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.