Triple
T36108058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EQA 300 4MATIC |
E1044416
|
entity |
| Predicate | powerOutputMetric |
P84509
|
FINISHED |
| Object | approximately 228 hp |
—
|
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: approximately 228 hp | Statement: [EQA 300 4MATIC, powerOutputMetric, approximately 228 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerOutputMetric Context triple: [EQA 300 4MATIC, powerOutputMetric, approximately 228 hp]
-
A.
powerOutputApprox
chosen
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
B.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
-
C.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
-
D.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
E.
powerOutputCharacteristic
Indicates the relationship between an entity and the specific way its power output behaves or is characterized under given conditions.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:08 p.m.