Triple
T2581420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontiac Solstice |
E57098
|
entity |
| Predicate | GXPFeature |
P29386
|
FINISHED |
| Object | turbocharged 2.0 L 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: turbocharged 2.0 L engine | Statement: [Pontiac Solstice, GXPFeature, turbocharged 2.0 L engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GXPFeature Context triple: [Pontiac Solstice, GXPFeature, turbocharged 2.0 L engine]
-
A.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
B.
isFeatureOf
chosen
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
C.
protectsFeature
Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of another entity.
-
D.
featuresCrossoverWith
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
E.
administrativeFeature
Indicates that one entity serves as an administrative or governance-related feature, function, or attribute associated with another entity.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3c843bc8190837cea3441bf3ca1 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.