Triple
T16663958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota ProAce City |
E404931
|
entity |
| Predicate | predecessorInToyotaRange |
P97
|
FINISHED |
| Object | Toyota Verso-based small vans |
—
|
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: Toyota Verso-based small vans | Statement: [Toyota ProAce City, predecessorInToyotaRange, Toyota Verso-based small vans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInToyotaRange Context triple: [Toyota ProAce City, predecessorInToyotaRange, Toyota Verso-based small vans]
-
A.
predecessorRiding
Indicates that one entity is riding or mounted on another entity that is its predecessor in some defined sequence or ordering.
-
B.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
C.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
D.
predecessorFranchise
Indicates that one franchise directly precedes and is succeeded by another franchise in a series or lineage.
-
E.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9afd048190b73bbc9c423915ca |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.