Triple
T30435267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Fuel Management |
E774291
|
entity |
| Predicate | deactivationCondition |
P64498
|
FINISHED |
| Object | high engine load |
—
|
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: high engine load | Statement: [Active Fuel Management, deactivationCondition, high engine load]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deactivationCondition Context triple: [Active Fuel Management, deactivationCondition, high engine load]
-
A.
canBeDeactivatedBy
Indicates that one entity has the ability or means to deactivate or disable another entity.
-
B.
deactivatedIn
Indicates that an entity has been turned off, disabled, or made inactive within a specified context, system, or time frame.
-
C.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
D.
deactivatedAt
Indicates the time or date at which an entity was disabled, turned off, or made inactive.
-
E.
removalCondition
chosen
Indicates the condition or circumstances under which an entity is removed, deleted, or no longer considered applicable.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68693d1b481909053505550c07c9d |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:07 p.m.