Triple
T3737802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Zeta platform |
E79625
|
entity |
| Predicate | notablePerformanceApplication |
P36409
|
FINISHED |
| Object | high-performance V8 sedans |
—
|
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-performance V8 sedans | Statement: [GM Zeta platform, notablePerformanceApplication, high-performance V8 sedans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePerformanceApplication Context triple: [GM Zeta platform, notablePerformanceApplication, high-performance V8 sedans]
-
A.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
B.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
C.
notablePrimaryPerformance
Indicates that an entity is recognized for a primary or leading performance in a work or event.
-
D.
hasNotablePerformance
chosen
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular context.
-
E.
notableLivePerformanceEvent
Indicates that an entity is a significant or widely recognized live performance event associated with another entity (such as an artist, work, or venue).
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3e9248819098d481fe29e1c628 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.