Triple
T34440385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwale |
E884078
|
entity |
| Predicate | hasNearbyResourceActivity |
P85424
|
FINISHED |
| Object | oil and gas production region |
—
|
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: oil and gas production region | Statement: [Kwale, hasNearbyResourceActivity, oil and gas production region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyResourceActivity Context triple: [Kwale, hasNearbyResourceActivity, oil and gas production region]
-
A.
hasNearbyEvent
Indicates that an event occurs close in space or time to the referenced entity.
-
B.
hasNearbyOperations
Indicates that an entity conducts operations or activities in locations that are geographically close to a specified reference point or area.
-
C.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
-
D.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
E.
nearbyActivity
chosen
Indicates that an activity occurs close in space or proximity to a specified entity or location.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 1, 2026, 2 a.m.