Triple
T35439281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PNG LNG project |
E1024296
|
entity |
| Predicate | feedGasField |
P116744
|
FINISHED |
| Object | Hides gas field |
—
|
NE NERFINISHED |
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: Hides gas field | Statement: [PNG LNG project, feedGasField, Hides gas field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedGasField Context triple: [PNG LNG project, feedGasField, Hides gas field]
-
A.
feedGasSource
chosen
Indicates that one entity serves as the supplying source of gas that is fed into another entity or process.
-
B.
keyGasField
Indicates that the subject is a primary or strategically important gas field in relation to the object (such as a region, company, or project).
-
C.
envelopeGas
Indicates that one entity serves as a surrounding gaseous layer or atmosphere enclosing another entity.
-
D.
containsGasField
Indicates that one entity geographically includes or encompasses a gas field within its boundaries.
-
E.
gasBlockFeature
Indicates a feature that prevents, restricts, or controls the movement or flow of gas between entities or regions.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795c0b0f48190b6edbf0eb5622c13 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.