Triple
T1366941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMC Yukon |
E30024
|
entity |
| Predicate | platform |
P1292
|
FINISHED |
| Object | GMT800 |
E7698
|
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: GMT800 | Statement: [GMC Yukon, platform, GMT800]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GMT800 Context triple: [GMC Yukon, platform, GMT800]
-
A.
GMT800
chosen
GMT800 is General Motors' full-size truck and SUV platform introduced in the late 1990s, underpinning vehicles like the Chevrolet Silverado and GMC Sierra.
-
B.
GMT400
GMT400 is General Motors’ full-size pickup and SUV platform produced from the late 1980s through the 1990s, underpinning vehicles like the Chevrolet C/K and GMC Sierra.
-
C.
GMT900
GMT900 is General Motors' full-size truck and SUV platform used for late-2000s models such as the Chevrolet Silverado and related vehicles.
-
D.
GMT360
GMT360 is General Motors' mid-size SUV platform used in the early 2000s for body-on-frame sport utility vehicles across several of its brands.
-
E.
GMT600 platform
The GMT600 platform is a General Motors architecture used for producing certain commercial vans and light-duty trucks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d33d2081908008494b5f56bf56 |
completed | March 1, 2026, 10:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acce788098819087a046e10966b7e9 |
completed | March 8, 2026, 1:18 a.m. |
Created at: March 1, 2026, 7:57 p.m.