Triple
T35425534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methanol Holdings (Trinidad) Limited |
E1023908
|
entity |
| Predicate | operatesContinuousProcessPlants |
P121503
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Methanol Holdings (Trinidad) Limited, operatesContinuousProcessPlants, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesContinuousProcessPlants Context triple: [Methanol Holdings (Trinidad) Limited, operatesContinuousProcessPlants, true]
-
A.
operatedPlantType
chosen
Indicates that an entity operates or manages a plant (facility) of a specified type.
-
B.
hasIndustrialPlant
Indicates that an entity possesses, operates, or is associated with an industrial plant facility.
-
C.
operatedPowerPlants
Indicates that an entity has managed, controlled, or run the operations of one or more power plants.
-
D.
hasProductionFacilitiesIn
Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
-
E.
operatedFacilitiesIn
Indicates that an entity has managed or run facilities located within a specified place or jurisdiction.
- 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_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
Created at: May 3, 2026, 4:03 p.m.