Triple
T14937617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamal LNG |
E372435
|
entity |
| Predicate | firstLNGShipment |
P101285
|
FINISHED |
| Object | December 2017 |
—
|
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: December 2017 | Statement: [Yamal LNG, firstLNGShipment, December 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLNGShipment Context triple: [Yamal LNG, firstLNGShipment, December 2017]
-
A.
firstShip
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
B.
firstShippedWith
Indicates that one entity was the initial product, version, or item to be delivered, released, or included together with another entity.
-
C.
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.
-
D.
firstFlightPayload
Indicates that the object is the payload carried on an entity’s first flight.
-
E.
firstOperationalCargoMissionDate
chosen
Indicates the calendar date on which an entity conducted its first operational mission carrying cargo.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:38 a.m.