Triple
T29716858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Browne gas field |
E751933
|
entity |
| Predicate | isSubsurfaceStructure |
P172163
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Browne gas field, isSubsurfaceStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubsurfaceStructure Context triple: [Browne gas field, isSubsurfaceStructure, true]
-
A.
hasSubsurfacePlatforms
Indicates that an entity includes or is equipped with platforms located below the surface or underground.
-
B.
hasSubsurfaceLines
Indicates that an entity possesses lines or features located beneath its visible surface.
-
C.
hasSubaerialExpression
Indicates that a geological feature formed or deposited underwater is exposed or expressed at the Earth’s surface above water.
-
D.
isSubstrateOf
Indicates that one entity serves as the material or reactant upon which another entity (typically an enzyme or process) acts in a chemical or biochemical reaction.
-
E.
subsurfaceSamplingDevice
Indicates a device is used to collect or sample materials from beneath a surface, such as soil, rock, or sediment layers.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 7:34 p.m.