Triple
T31236923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baydaratskaya Bay |
E796449
|
entity |
| Predicate | nearbyResourceType |
P72516
|
FINISHED |
| Object | natural gas fields |
—
|
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: natural gas fields | Statement: [Baydaratskaya Bay, nearbyResourceType, natural gas fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyResourceType Context triple: [Baydaratskaya Bay, nearbyResourceType, natural gas fields]
-
A.
nearbyResourcePotential
chosen
Indicates that a resource is likely available or exploitable in the vicinity of the referenced entity or location.
-
B.
nearbyFacilityType
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
C.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
D.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
E.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 29, 2026, 9:11 p.m.