Triple
T29401133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichthys LNG development |
E745644
|
entity |
| Predicate | LPGCapacity |
P166738
|
FINISHED |
| Object | approximately 1.6 million tonnes per annum |
—
|
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: approximately 1.6 million tonnes per annum | Statement: [Ichthys LNG development, LPGCapacity, approximately 1.6 million tonnes per annum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LPGCapacity Context triple: [Ichthys LNG development, LPGCapacity, approximately 1.6 million tonnes per annum]
-
A.
LPGCapacity_MTPA
chosen
Indicates the liquefied petroleum gas (LPG) handling or storage capacity measured in million tonnes per annum (MTPA).
-
B.
LNGCapacity_MTPA
Indicates the liquefied natural gas processing or export capacity measured in million tonnes per annum (MTPA).
-
C.
fuelCapacityLiters
Indicates the amount of fuel a vehicle or container can hold, measured in liters.
-
D.
fuelCapacityKg
Indicates the maximum amount of fuel an entity can hold, measured in kilograms.
-
E.
designCapacityLNGWithTrain7
Indicates the liquefied natural gas (LNG) design production capacity specifically associated with train 7 of a facility.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a0772648190b5083f0fa099137c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:51 p.m.