Triple
T21819963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamnagar refinery complex |
E538699
|
entity |
| Predicate | refiningCapacity |
P122488
|
FINISHED |
| Object | over 1.2 million 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 1.2 million barrels per day | Statement: [Jamnagar refinery complex, refiningCapacity, over 1.2 million barrels per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refiningCapacity Context triple: [Jamnagar refinery complex, refiningCapacity, over 1.2 million barrels per day]
-
A.
refiningCapacityBarrelsPerDayApprox
chosen
Indicates the approximate amount of crude oil a refinery can process, measured in barrels per day.
-
B.
productionCapacity
Indicates the maximum amount of output an entity can produce within a given time or resource constraint.
-
C.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
D.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
E.
capacityPerHour
Indicates the maximum amount of output or throughput an entity can handle or produce in one hour.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cce0b8081909e20ded72db40304 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.