Triple
T23169039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hibernia oil field |
E578792
|
entity |
| Predicate | platformFunction |
P80820
|
FINISHED |
| Object | oil drilling |
—
|
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 drilling | Statement: [Hibernia oil field, platformFunction, oil drilling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformFunction Context triple: [Hibernia oil field, platformFunction, oil drilling]
-
A.
platformInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or communicates with a broader platform or system.
-
B.
relatedPlatformFunction
Indicates that one platform function is associated with, complements, or is otherwise functionally connected to another platform function.
-
C.
platformMate
Indicates that two entities are located on the same platform or share the same platform context at a given time.
-
D.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
-
E.
projectFunction
chosen
Indicates that an entity serves as a function, role, or operational purpose within a project.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2e5e208190839ec37de4b974af |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.