Triple
T17282099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burmah Oil Company |
E419556
|
entity |
| Predicate | operatedFacilities |
P4904
|
FINISHED |
| Object | oil fields in Burma |
—
|
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 fields in Burma | Statement: [Burmah Oil Company, operatedFacilities, oil fields in Burma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedFacilities Context triple: [Burmah Oil Company, operatedFacilities, oil fields in Burma]
-
A.
operatesFacility
chosen
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
D.
facilityOperatedBy
Indicates that a facility is managed, run, or controlled by a specified agent or organization.
-
E.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332a4c008190b44f4145d0e94a21 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.