Triple
T6598558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studebaker Avanti |
E148537
|
entity |
| Predicate | highPerformanceVersion |
P12592
|
FINISHED |
| Object | R3 engine |
—
|
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: R3 engine | Statement: [Studebaker Avanti, highPerformanceVersion, R3 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highPerformanceVersion Context triple: [Studebaker Avanti, highPerformanceVersion, R3 engine]
-
A.
notableHighPerformanceVariant
chosen
Indicates that an entity is recognized as a particularly high-performance version or variant of another entity.
-
B.
poweredVersionOf
Indicates that one entity is a more powerful, enhanced, or upgraded version of another entity.
-
C.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
openedAsHighSpeed
Indicates that something was inaugurated or began operation specifically as a high-speed service or facility.
-
E.
performancePackage
Indicates that an entity is associated with a specific performance-related bundle or configuration, typically grouping features or enhancements that affect its performance.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:56 p.m.