Triple
T36277943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluto LNG |
E892856
|
entity |
| Predicate | gasFieldDistanceOffshore |
P185087
|
FINISHED |
| Object | approximately 190 kilometres |
—
|
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 190 kilometres | Statement: [Pluto LNG, gasFieldDistanceOffshore, approximately 190 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasFieldDistanceOffshore Context triple: [Pluto LNG, gasFieldDistanceOffshore, approximately 190 kilometres]
-
A.
nauticalDistance
Indicates the measured distance between two locations or entities expressed in nautical units (typically nautical miles).
-
B.
offshoreDistanceFromHokkaido_km
Indicates the distance, in kilometers, that something is located offshore from the coast of Hokkaido.
-
C.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
D.
distanceToGulfOfMexico
Indicates the measured or estimated spatial distance between a given location and the Gulf of Mexico.
-
E.
offshoreFeature
Indicates that a geographic or structural feature is located in a marine or aquatic area away from the shoreline.
- F. None of above. chosen
Provenance (4 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.