Triple
T9119580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2.5L Duratec inline-4 |
E218808
|
entity |
| Predicate | intakeSystem |
P21444
|
FINISHED |
| Object | multi-runner intake manifold |
—
|
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: multi-runner intake manifold | Statement: [2.5L Duratec inline-4, intakeSystem, multi-runner intake manifold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intakeSystem Context triple: [2.5L Duratec inline-4, intakeSystem, multi-runner intake manifold]
-
A.
intake
Indicates the act of taking something in or consuming it, such as food, drink, or other substances, into a system or organism.
-
B.
airIntakeType
chosen
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
-
C.
intakeLocation
Indicates the place or facility where an entity is initially received, admitted, or taken in.
-
D.
airIntakeLocation
Indicates the physical position or area where air is drawn into a system, device, or structure.
-
E.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a902e08190a7eb4728f32b9e1d |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.