Triple
T8866146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 918 Spyder |
E211022
|
entity |
| Predicate | powerOutputSystem |
P84509
|
FINISHED |
| Object | over 880 PS |
—
|
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: over 880 PS | Statement: [Porsche 918 Spyder, powerOutputSystem, over 880 PS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerOutputSystem Context triple: [Porsche 918 Spyder, powerOutputSystem, over 880 PS]
-
A.
powerOutputApprox
chosen
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
B.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
C.
designPowerOutput
Indicates the intended or specified power output level that something is designed to produce under defined conditions.
-
D.
powerInterface
Indicates that one entity serves as a power-providing interface or connection point for another entity, enabling the transfer or supply of electrical power.
-
E.
powerFeeding
Indicates a relationship where one entity supplies electrical power to another entity for its operation or charging.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6106d41081909db710bda8aaf6fd |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.