Triple
T10594913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J80 |
E250083
|
entity |
| Predicate | usedForModelYearsApprox |
P4161
|
FINISHED |
| Object | early 1990s to late 1990s |
—
|
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: early 1990s to late 1990s | Statement: [J80, usedForModelYearsApprox, early 1990s to late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForModelYearsApprox Context triple: [J80, usedForModelYearsApprox, early 1990s to late 1990s]
-
A.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
-
B.
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.
-
C.
approximateDesignYear
Indicates the estimated or inferred year in which something was designed, rather than a precisely known design year.
-
D.
usedForSeasonRange
Indicates the span of seasons or time period during which something is intended or suitable to be used.
-
E.
lastAppearanceYear
Indicates the calendar year in which an entity made its most recent appearance.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278cbf9081909ef419b0144d5019 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.