Triple
T23197317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SeaRose FPSO |
E579906
|
entity |
| Predicate | resourceProduced |
P76326
|
FINISHED |
| Object | crude oil |
—
|
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: crude oil | Statement: [SeaRose FPSO, resourceProduced, crude oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceProduced Context triple: [SeaRose FPSO, resourceProduced, crude oil]
-
A.
commodityProduced
chosen
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
B.
usesProductionResourcesOf
Indicates that one entity makes use of the production resources (such as facilities, equipment, or infrastructure) that belong to or are operated by another entity.
-
C.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
D.
productionBy
Indicates that something is created, manufactured, or generated by a particular agent, organization, or process.
-
E.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
- 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.