Triple
T17072330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Santa Fe |
E414252
|
entity |
| Predicate | thirdGenerationLaunchYear |
P25155
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Hyundai Santa Fe, thirdGenerationLaunchYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdGenerationLaunchYear Context triple: [Hyundai Santa Fe, thirdGenerationLaunchYear, 2012]
-
A.
thirdGenerationReleaseDate
Indicates the date on which the third generation of an item, product, or entity was officially released.
-
B.
thirdGenerationMarketedAs
Indicates that something is promoted or labeled as being in its third generation within a series or product line.
-
C.
thirdGenerationStart
chosen
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
D.
thirdGeneration
Indicates that one entity is the grandchild (third generation) relative to another entity in a lineage or succession.
-
E.
fourthGenerationReleaseDate
Indicates the date on which the fourth generation of an item, product, or entity was released.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc1b7d48190979a848b4188cb22 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.