Triple
T1823898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT400 |
E40606
|
entity |
| Predicate | usedForModelYears |
P4161
|
FINISHED |
| Object | 1988 model year |
—
|
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: 1988 model year | Statement: [GMT400, usedForModelYears, 1988 model year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForModelYears Context triple: [GMT400, usedForModelYears, 1988 model year]
-
A.
modelYears
chosen
Indicates the association between a product (often a vehicle or device) and the specific calendar years in which that model version was produced or marketed.
-
B.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
-
C.
isUsedAllYear
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
-
D.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
E.
purchaseYear
Indicates the calendar year in which a purchase or acquisition of something took place.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab21ab83a48190a33afe5db19a21f8 |
completed | March 6, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61d97d008190b6642aef32eb7e36 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.