Triple
T37108166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energy Corporation |
E918906
|
entity |
| Predicate | impliesActivity |
P48591
|
FINISHED |
| Object | involvement in energy supply chain |
—
|
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: involvement in energy supply chain | Statement: [Energy Corporation, impliesActivity, involvement in energy supply chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesActivity Context triple: [Energy Corporation, impliesActivity, involvement in energy supply chain]
-
A.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
B.
impliesEvent
Indicates that one event logically leads to, entails, or guarantees the occurrence of another event.
-
C.
impliesStatus
Indicates that one condition, fact, or state logically leads to or determines another status or outcome.
-
D.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
E.
associatedActivity
chosen
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.