Triple
T8630489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 959 |
E204387
|
entity |
| Predicate | engineAspiration |
P84513
|
FINISHED |
| Object | twin-turbocharged |
—
|
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: twin-turbocharged | Statement: [Porsche 959, engineAspiration, twin-turbocharged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineAspiration Context triple: [Porsche 959, engineAspiration, twin-turbocharged]
-
A.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
B.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
C.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
engineDisplacement
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
- 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_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. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:27 p.m.