Triple
T23168753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMDC |
E578784
|
entity |
| Predicate | fieldTypeManaged |
P51437
|
FINISHED |
| Object | offshore oil field |
—
|
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: offshore oil field | Statement: [HMDC, fieldTypeManaged, offshore oil field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldTypeManaged Context triple: [HMDC, fieldTypeManaged, offshore oil field]
-
A.
fieldType
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
B.
fieldManager
Indicates that one entity serves as the manager or overseer responsible for operations, activities, or resources within a particular field or domain of another entity.
-
C.
typeOfPropertyManaged
chosen
Indicates the specific category or kind of property that an entity is responsible for managing.
-
D.
standardTypeManaged
Indicates that an entity is governed, controlled, or handled according to a defined standard type or classification.
-
E.
fieldComponent
Indicates that one entity functions as a constituent or sub-part within a larger field or domain defined 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_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.