Triple
T16848467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hound Point Terminal |
E409606
|
entity |
| Predicate | receivesOilFrom |
P125095
|
FINISHED |
| Object | North Sea oil fields |
—
|
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: North Sea oil fields | Statement: [Hound Point Terminal, receivesOilFrom, North Sea oil fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesOilFrom Context triple: [Hound Point Terminal, receivesOilFrom, North Sea oil fields]
-
A.
oilSystem
Indicates a relationship where an entity functions as, is part of, or is associated with an oil-based system used for lubrication, operation, or processing.
-
B.
hasOilTerminal
Indicates that one entity possesses, hosts, or contains an oil terminal used for storing or transferring oil.
-
C.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
D.
hasLubricationMethod
Indicates the method or technique by which lubrication is applied or provided in a given context.
-
E.
oilType
Indicates the specific kind or classification of oil associated with an 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b376bac48190ae09f29a28c55f8c |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:24 a.m.