Triple
T14511142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Field LNG projects |
E340396
|
entity |
| Predicate | basedOnField |
P7446
|
FINISHED |
| Object | world’s largest non-associated gas field |
—
|
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: world’s largest non-associated gas field | Statement: [North Field LNG projects, basedOnField, world’s largest non-associated gas field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnField Context triple: [North Field LNG projects, basedOnField, world’s largest non-associated gas field]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
basedOnValues
Indicates that something is determined, derived, or decided according to specified values or value-based criteria.
-
C.
basedOnType
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
D.
basedOnText
Indicates that something is derived, adapted, or developed from a specific text source.
-
E.
areBasedOn
chosen
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e5b7b48190878be271840c265b |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.