Triple
T30533365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 992 GT3 |
E777068
|
entity |
| Predicate | aeroFeature |
P19885
|
FINISHED |
| Object | large fixed rear wing |
—
|
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: large fixed rear wing | Statement: [Porsche 992 GT3, aeroFeature, large fixed rear wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aeroFeature Context triple: [Porsche 992 GT3, aeroFeature, large fixed rear wing]
-
A.
aerodynamicsFeature
chosen
Indicates that one entity possesses or is characterized by a specific aerodynamic property, component, or design feature affecting airflow and motion through air.
-
B.
aircraftDesignFeature
Indicates a relationship where a specific design feature is associated with, or incorporated into, an aircraft.
-
C.
isAerial
Indicates that one entity operates or exists in the air relative to another entity or context.
-
D.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
E.
airportFeature
Indicates that an airport possesses or is characterized by a particular feature, facility, or attribute.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6884deb64819083f346e9ac4824ba |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:18 p.m.