Triple
T23197325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SeaRose FPSO |
E579906
|
entity |
| Predicate | storageCapability |
P105108
|
FINISHED |
| Object | floating crude oil storage |
—
|
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: floating crude oil storage | Statement: [SeaRose FPSO, storageCapability, floating crude oil storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageCapability Context triple: [SeaRose FPSO, storageCapability, floating crude oil storage]
-
A.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
B.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
C.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
D.
storageDevice
Indicates a relationship where one entity functions as a device used to store data or digital information for another entity.
-
E.
storageProperty
chosen
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fdc0b8081909242fdc5cb1da517 |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.