Triple
T35784972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle GM Nationals |
E1034539
|
entity |
| Predicate | typicalVehicleBrandsShown |
P58194
|
FINISHED |
| Object | Chevrolet |
E4515
|
NE 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: Chevrolet | Statement: [Carlisle GM Nationals, typicalVehicleBrandsShown, Chevrolet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVehicleBrandsShown Context triple: [Carlisle GM Nationals, typicalVehicleBrandsShown, Chevrolet]
-
A.
vehicleBrandAssociated
Indicates that there is an association or linkage between a vehicle and a particular brand.
-
B.
vehicleManufacturerHosted
Indicates that a vehicle manufacturer organized, sponsored, or served as the host for a particular event or activity.
-
C.
fieldedCarBrand
chosen
Indicates that a particular car brand has been entered, deployed, or represented (e.g., in a race, event, or lineup) by some agent or organization.
-
D.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
E.
carManufacturer
Indicates that one entity is the company that produces or manufactures the car represented by the other entity.
- F. None of above.
Provenance (4 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38860b19ec81908e591fb1ebb252e7 |
completed | June 22, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.