Triple
T9106258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motiva Enterprises |
E218484
|
entity |
| Predicate | refineryCapacity |
P80385
|
FINISHED |
| Object | over 600,000 barrels per day |
—
|
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: over 600,000 barrels per day | Statement: [Motiva Enterprises, refineryCapacity, over 600,000 barrels per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refineryCapacity Context triple: [Motiva Enterprises, refineryCapacity, over 600,000 barrels per day]
-
A.
hasRefinery
Indicates that one entity possesses, operates, or is associated with a refinery facility used for processing raw materials.
-
B.
unitCapacity
chosen
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
C.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
D.
capacityPerHour
Indicates the maximum amount of output or throughput an entity can handle or produce in one hour.
-
E.
refineryOperator
Indicates that one entity operates, manages, or runs a refinery facility for another entity or in a given context.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57286a88190b256d2461c5c0aed |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.