Triple
T35603403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangala oil field |
E1028815
|
entity |
| Predicate | licenseBlockOperator |
P183450
|
FINISHED |
| Object | Cairn Oil & Gas |
—
|
NE NERFINISHED |
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: Cairn Oil & Gas | Statement: [Mangala oil field, licenseBlockOperator, Cairn Oil & Gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseBlockOperator Context triple: [Mangala oil field, licenseBlockOperator, Cairn Oil & Gas]
-
A.
licenseBlock
Indicates that an entity is prohibited or restricted from using a license or licensed resource.
-
B.
licenceBuiltIn
Indicates that a licence is inherently included within or comes pre-installed as part of another product, system, or component rather than being added separately.
-
C.
licenseStewardship
Indicates that one entity is responsible for managing, overseeing, or administering a license on behalf of another entity.
-
D.
licenseBuiltIn
Indicates that a license is inherently included within or comes standard as part of another product, service, or system rather than being added separately.
-
E.
licenseAuthor
Indicates that one entity is the author or originator of a license granted to another entity.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.