Triple
T13289589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors GMT platform family |
E316532
|
entity |
| Predicate | notableVariant |
P4680
|
FINISHED |
| Object | GMT305 |
E505263
|
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: GMT305 | Statement: [General Motors GMT platform family, notableVariant, GMT305]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GMT305 Context triple: [General Motors GMT platform family, notableVariant, GMT305]
-
A.
GMT305
chosen
GMT305 is General Motors' mid-size SUV platform that underpinned vehicles such as the GMC Envoy.
-
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.
GMT330
GMT330 is General Motors' mid-size SUV platform that underpinned vehicles such as the GMC Envoy.
-
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.
GMT361
GMT361 is a model in General Motors' GMT platform line of full-size vehicles that followed the GMT360 architecture.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99076aeec8190b0cb883ab60d3f6b |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716d4a6f48190a2020e11e887be2e |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:27 p.m.