Triple
T5702953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corvette Summer |
E125713
|
entity |
| Predicate | vehicleFeatured |
P16722
|
FINISHED |
| Object | customized Chevrolet Corvette |
—
|
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: customized Chevrolet Corvette | Statement: [Corvette Summer, vehicleFeatured, customized Chevrolet Corvette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleFeatured Context triple: [Corvette Summer, vehicleFeatured, customized Chevrolet Corvette]
-
A.
featuresVehicle
chosen
Indicates that one entity includes, presents, or prominently incorporates a particular vehicle as part of its content, composition, or offering.
-
B.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
C.
vehicleName
Indicates the specific name or designation assigned to a vehicle.
-
D.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
E.
vehicleDeveloped
Indicates that an entity (such as a person, organization, or group) created, designed, or otherwise developed a particular vehicle.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02456efb48190bf3aaabcc77cda92 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.