Triple
T9072292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westview Wood Pellet Terminal |
E217396
|
entity |
| Predicate | materialTypeHandled |
P28567
|
FINISHED |
| Object | compressed sawdust pellets |
—
|
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: compressed sawdust pellets | Statement: [Westview Wood Pellet Terminal, materialTypeHandled, compressed sawdust pellets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialTypeHandled Context triple: [Westview Wood Pellet Terminal, materialTypeHandled, compressed sawdust pellets]
-
A.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
B.
handlesMaterial
chosen
Indicates that an entity is responsible for managing, processing, or otherwise dealing with a specified material.
-
C.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
-
D.
supportsMaterial
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
E.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ffa04819086be5763133c5067 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.