Triple
T10042044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTU MB 838 CaM 500 |
E205317
|
entity |
| Predicate | designedToOperateOn |
P90642
|
FINISHED |
| Object | diesel fuel |
—
|
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: diesel fuel | Statement: [MTU MB 838 CaM 500, designedToOperateOn, diesel fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToOperateOn Context triple: [MTU MB 838 CaM 500, designedToOperateOn, diesel fuel]
-
A.
operatesPrimarilyOn
chosen
Indicates that one entity is mainly or chiefly used to act upon, affect, or process another entity.
-
B.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
C.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
operatesUnitType
Indicates that an entity runs, manages, or controls a unit of a specified type.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.