Triple
T8631766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daimler-Benz DB 603A |
E204418
|
entity |
| Predicate | powerToWeightCharacteristic |
P6069
|
FINISHED |
| Object | high power output for its time |
—
|
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 power output for its time | Statement: [Daimler-Benz DB 603A, powerToWeightCharacteristic, high power output for its time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerToWeightCharacteristic Context triple: [Daimler-Benz DB 603A, powerToWeightCharacteristic, high power output for its time]
-
A.
vehiclePower
Indicates the amount or type of power a vehicle can produce or is rated to deliver.
-
B.
enginePower
chosen
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
C.
powerRange
Indicates the range of power values within which an entity operates, applies, or is considered valid.
-
D.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
-
E.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.