Triple
T29401010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calliance gas field |
E745640
|
entity |
| Predicate | plannedExportRoute |
P82020
|
FINISHED |
| Object | LNG export via Browse LNG project |
—
|
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: LNG export via Browse LNG project | Statement: [Calliance gas field, plannedExportRoute, LNG export via Browse LNG project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedExportRoute Context triple: [Calliance gas field, plannedExportRoute, LNG export via Browse LNG project]
-
A.
plannedVia
chosen
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
B.
initialScheduledRoute
Indicates that an entity is assigned to follow a specific route as originally planned or scheduled, before any changes or updates.
-
C.
plannedTransit
Indicates that a transit or trip has been scheduled or arranged to occur, but has not yet taken place.
-
D.
plannedMode
Indicates that a particular mode, method, or state has been intentionally selected or scheduled in advance for use.
-
E.
plannedFrom
Indicates that something is scheduled or arranged to originate, start, or be derived from a specified source, time, or condition.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 2:51 p.m.