Triple
T2482814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohat |
E55857
|
entity |
| Predicate | hasNearbyResource |
P18252
|
FINISHED |
| Object | oil and 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: oil and gas fields | Statement: [Kohat, hasNearbyResource, oil and gas fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyResource Context triple: [Kohat, hasNearbyResource, oil and gas fields]
-
A.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
B.
hasNearbyMode
chosen
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
-
D.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
-
E.
hasNearbySquare
Indicates that one entity has at least one square-shaped entity located close to it in 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.