Triple
T23001407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Matrix |
E572640
|
entity |
| Predicate | primaryBodyStyleMarketedAs |
P150601
|
FINISHED |
| Object | crossover-hatchback |
—
|
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: crossover-hatchback | Statement: [Toyota Matrix, primaryBodyStyleMarketedAs, crossover-hatchback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBodyStyleMarketedAs Context triple: [Toyota Matrix, primaryBodyStyleMarketedAs, crossover-hatchback]
-
A.
primaryBodyStyle
Indicates the main or predominant body configuration or structural form associated with an entity.
-
B.
primaryStyle
Indicates the main or predominant style associated with an entity, distinguishing it from other secondary or supporting styles.
-
C.
primaryBody
Indicates that one entity serves as the main or principal body associated with another entity.
-
D.
bodyStyleCategory
Indicates the general body style classification or category that an item (such as a vehicle or product) belongs to.
-
E.
secondaryBodyStyle
Indicates a secondary or additional body style associated with an entity, complementing its primary body style classification.
- F. None of above. chosen
Provenance (4 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18353d05481909abacb48a14ef21e |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.