Triple
T29400979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brecknock gas field |
E745639
|
entity |
| Predicate | hasDevelopmentPotentialFor |
P58576
|
FINISHED |
| Object | offshore 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: offshore LNG project | Statement: [Brecknock gas field, hasDevelopmentPotentialFor, offshore LNG project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevelopmentPotentialFor Context triple: [Brecknock gas field, hasDevelopmentPotentialFor, offshore LNG project]
-
A.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
B.
hasPotential
chosen
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
-
C.
hasDevelopmentActor
Indicates that an entity is associated with or supported by a specific actor responsible for its development or advancement.
-
D.
canDevelop
Indicates that one entity has the ability or capacity to develop, create, or build another entity.
-
E.
isDevelopmentOf
Indicates that one entity is the development, evolution, or more advanced form derived from 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 28, 2026, 2:51 p.m.