Triple
T35698412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingenium diesel engine |
E1031505
|
entity |
| Predicate | designedGoal |
P143170
|
FINISHED |
| Object | reduced CO2 emissions |
—
|
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: reduced CO2 emissions | Statement: [Ingenium diesel engine, designedGoal, reduced CO2 emissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedGoal Context triple: [Ingenium diesel engine, designedGoal, reduced CO2 emissions]
-
A.
lifetimeDesignGoal
Indicates a design objective or target that is intended to be maintained or achieved over the entire lifetime of the system or product.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
benefitDesignGoal
Indicates that something contributes positively toward achieving a particular design goal.
-
D.
overallDesignGoal
Indicates that one entity specifies or represents the primary design objective or guiding design intent for another entity.
-
E.
goalOfRealization
chosen
Indicates the intended outcome or objective that an action, process, or plan is meant to bring into reality or achieve.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.