Triple
T14937625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamal LNG |
E372435
|
entity |
| Predicate | usesTankerType |
P46290
|
FINISHED |
| Object | Arc7 ice-class LNG carrier |
—
|
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: Arc7 ice-class LNG carrier | Statement: [Yamal LNG, usesTankerType, Arc7 ice-class LNG carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTankerType Context triple: [Yamal LNG, usesTankerType, Arc7 ice-class LNG carrier]
-
A.
hasTankerClass
chosen
Indicates that an entity is associated with, or belongs to, a particular class or category of tanker.
-
B.
hasTankType
Indicates that an entity is associated with, or classified by, a specific type or category of tank.
-
C.
hasTank
Indicates that an entity possesses, is equipped with, or contains a tank (such as a storage tank, fuel tank, or similar vessel).
-
D.
primaryTankerModel
Indicates that one entity is the main or standard tanker model associated with another entity (such as a product line, fleet, or organization).
-
E.
usedExternalTank
Indicates that an entity made use of an external tank as part of its operation or activity.
- 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.