Triple
T17072332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Santa Fe |
E414252
|
entity |
| Predicate | fifthGenerationLaunchYear |
P25546
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Hyundai Santa Fe, fifthGenerationLaunchYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifthGenerationLaunchYear Context triple: [Hyundai Santa Fe, fifthGenerationLaunchYear, 2023]
-
A.
fifthGenerationLaunch
Indicates the event or action of initiating or releasing something that belongs to its fifth generation in a series or product line.
-
B.
fifthGenerationStart
chosen
Indicates the point in time or event at which the fifth generation in a sequence, lineage, or series begins.
-
C.
fifthGeneration
Indicates that one entity belongs to the fifth generation in a lineage, sequence, or series relative to another entity.
-
D.
fifthGenerationEnd
Indicates that a lineage, process, or sequence has reached the end of its fifth generation.
-
E.
sixthGenerationEndYear
Indicates the year in which a sixth generation (e.g., of a product, lineage, or series) comes to an end.
- 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.