Triple
T29400935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichthys gas field |
E745638
|
entity |
| Predicate | exportPipelineLength_km |
P129716
|
FINISHED |
| Object | approximately 890 |
—
|
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 890 | Statement: [Ichthys gas field, exportPipelineLength_km, approximately 890]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportPipelineLength_km Context triple: [Ichthys gas field, exportPipelineLength_km, approximately 890]
-
A.
pipelineLength
chosen
Indicates the total physical length of a pipeline connecting two or more points.
-
B.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
C.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
-
D.
mainStraightLengthKm
Indicates the length, measured in kilometers, of the primary straight segment associated with the entity.
-
E.
plannedTransmissionLineLength
Indicates the intended or projected length of a transmission line as specified in a plan or design.
- 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:50 p.m.