Triple
T31948192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mellitah Oil and Gas |
E815707
|
entity |
| Predicate | onshoreRegion |
P12445
|
FINISHED |
| Object | Libyan desert |
—
|
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: Libyan desert | Statement: [Mellitah Oil and Gas, onshoreRegion, Libyan desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onshoreRegion Context triple: [Mellitah Oil and Gas, onshoreRegion, Libyan desert]
-
A.
onshoreOrOffshore
Indicates whether something is located or occurring on land (onshore) or at sea/away from land (offshore).
-
B.
overseasRegionOf
Indicates that one region is an overseas territory or administrative division belonging to another country or primary region.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b27b51c88190b56dc3f22f934aff |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.