Triple
T35425495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCS Nitrogen Trinidad Limited |
E1023907
|
entity |
| Predicate | hasOperationalRisk |
P136373
|
FINISHED |
| Object | natural gas supply disruptions |
—
|
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: natural gas supply disruptions | Statement: [PCS Nitrogen Trinidad Limited, hasOperationalRisk, natural gas supply disruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationalRisk Context triple: [PCS Nitrogen Trinidad Limited, hasOperationalRisk, natural gas supply disruptions]
-
A.
hasRiskStatus
Indicates the level or category of risk currently associated with an entity.
-
B.
hasOperationalSignificance
Indicates that something plays a meaningful, practical role or effect in how a system, process, or operation functions or is carried out.
-
C.
hasRiskFrom
chosen
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
D.
riskAssessmentBy
Indicates that a risk assessment is performed, evaluated, or provided by a specific agent or entity.
-
E.
hasRiskyStrategy
Indicates that an entity employs or is associated with a strategy characterized by a high level of risk or potential for significant loss.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.