Triple
T30435227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM small-block engine family |
E774290
|
entity |
| Predicate | laterInductionSystem |
P198520
|
FINISHED |
| Object | fuel injected |
—
|
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: fuel injected | Statement: [GM small-block engine family, laterInductionSystem, fuel injected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterInductionSystem Context triple: [GM small-block engine family, laterInductionSystem, fuel injected]
-
A.
inductionSystem
Indicates a relationship where an entity functions as or is associated with an induction-based system (e.g., using electromagnetic induction for operation or control).
-
B.
laterGoverningSystem
Indicates that one governing system succeeds and replaces another at a later point in time.
-
C.
positionOnInduction
Indicates a stance, view, or policy that an entity holds regarding the use or validity of inductive reasoning or induction-based methods.
-
D.
typicalInductionSystem
Indicates that one entity is a standard or representative example of an induction system associated with another entity.
-
E.
hasInductionSchedule
Indicates that an entity is associated with a defined plan or timetable for its induction or onboarding process.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_69fef1112b0c8190a8eb027edb71e4e0 |
completed | May 9, 2026, 8:32 a.m. |
Created at: April 29, 2026, 8:07 p.m.