Triple
T35439289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PNG LNG project |
E1024296
|
entity |
| Predicate | firstLNGCargo |
P101282
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [PNG LNG project, firstLNGCargo, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLNGCargo Context triple: [PNG LNG project, firstLNGCargo, 2014]
-
A.
firstOperationalCargoMission
Indicates that the subject entity is the earliest or initial cargo mission to be put into operational service for the related program, system, or route.
-
B.
firstFlightPayload
Indicates that the object is the payload carried on an entity’s first flight.
-
C.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
D.
firstCargoMissionProgram
chosen
Indicates that the subject is the first cargo mission within a given program or series of missions.
-
E.
LNGTrains
Indicates a relationship where liquefied natural gas (LNG) is processed, handled, or transported via specific LNG train units or facilities.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.