Triple
T29401119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ichthys LNG development |
E745644
|
entity |
| Predicate | onshoreProcessingLocation |
P166740
|
FINISHED |
| Object | Bladin Point |
—
|
NE NERFINISHED |
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: Bladin Point | Statement: [Ichthys LNG development, onshoreProcessingLocation, Bladin Point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onshoreProcessingLocation Context triple: [Ichthys LNG development, onshoreProcessingLocation, Bladin Point]
-
A.
offshoreProcessingLocation
Indicates that an action, service, or operation is carried out at a location situated offshore, typically outside the primary or originating jurisdiction.
-
B.
onshoreOrOffshore
Indicates whether something is located or occurring on land (onshore) or at sea/away from land (offshore).
-
C.
onshoreConnectionPoint
Indicates a relationship where an offshore or marine asset is linked to a specific connection point located on land for transfer or integration purposes.
-
D.
commissioningLocation
Indicates the place where an entity (such as a work, project, or item) is formally commissioned or initiated.
-
E.
primaryPostingLocation
Indicates the main or default location where an entity (such as a message, job, or content item) is originally posted or primarily published.
- F. None of above. chosen
Provenance (4 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_69f66a0772648190b5083f0fa099137c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:51 p.m.