Triple
T2462592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Highlander |
E54565
|
entity |
| Predicate | fourthGenerationProduction |
P25157
|
FINISHED |
| Object | 2019–present |
—
|
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: 2019–present | Statement: [Toyota Highlander, fourthGenerationProduction, 2019–present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthGenerationProduction Context triple: [Toyota Highlander, fourthGenerationProduction, 2019–present]
-
A.
fourthGenerationName
Indicates that the object is the name assigned to an entity in the fourth generation of a lineage or sequence relative to the subject.
-
B.
fourthGenerationStart
chosen
Indicates the point in time or event at which a fourth generation in a sequence, lineage, or series begins.
-
C.
fourthGenerationReleaseDate
Indicates the date on which the fourth generation of an item, product, or entity was released.
-
D.
fourthGenerationEnd
Indicates that a lineage, process, or sequence has reached the end of its fourth generation.
-
E.
firstGenerationProduction
Indicates that the production or creation of something belongs to its initial or earliest generation in a sequence or lineage.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.