Triple
T9399189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3.5L Duratec V6 |
E226422
|
entity |
| Predicate | oilSystem |
P88724
|
FINISHED |
| Object | wet sump |
—
|
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: wet sump | Statement: [3.5L Duratec V6, oilSystem, wet sump]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oilSystem Context triple: [3.5L Duratec V6, oilSystem, wet sump]
-
A.
oilType
Indicates the specific kind or classification of oil associated with an entity.
-
B.
hydrocarbonSystem
Indicates a relationship where entities participate together in or belong to the same hydrocarbon system, such as a connected set of geological components involved in hydrocarbon generation, migration, and accumulation.
-
C.
oilContent
Indicates the amount or proportion of oil present in a given substance, material, or item.
-
D.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
E.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51556fc08190b8ff8190a1485a3a |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.