Triple
T18172830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota C-HR |
E435073
|
entity |
| Predicate | competitor |
P1375
|
FINISHED |
| Object | Mazda CX-3 |
—
|
NE NERFINISHED |
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: Mazda CX-3 | Statement: [Toyota C-HR, competitor, Mazda CX-3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mazda CX-3 Context triple: [Toyota C-HR, competitor, Mazda CX-3]
-
A.
Mazda CX-3
chosen
The Mazda CX-3 is a subcompact crossover SUV known for its sporty handling, stylish design, and fuel-efficient Skyactiv powertrain.
-
B.
Mazda CX-30
The Mazda CX-30 is a compact crossover SUV known for its sleek design, upscale interior, and engaging driving dynamics within Mazda’s lineup.
-
C.
Mazda CX-5
The Mazda CX-5 is a compact crossover SUV known for its stylish design, engaging driving dynamics, and efficient Skyactiv technology.
-
D.
Mazda CX-50 (in some markets/segments)
The Mazda CX-50 is a compact crossover SUV positioned as a more rugged, adventure-oriented companion to Mazda’s CX-5, featuring bolder styling and enhanced off-road capability for certain markets.
-
E.
Mazda CX-8
The Mazda CX-8 is a mid-size three-row crossover SUV known for its efficient performance, refined driving dynamics, and upscale interior.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df56d0a88190af3f407d2a3bb74f |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 10:30 a.m.