Triple

T10373608
Position Surface form Disambiguated ID Type / Status
Subject Mazda MX-6 E244445 entity
Predicate relatedTo P37 FINISHED
Object Mazda 626 E727429 NE 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: Mazda 626 | Statement: [Mazda MX-6, relatedTo, Mazda 626]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mazda 626
Context triple: [Mazda MX-6, relatedTo, Mazda 626]
  • A. Mazda 626 chosen
    The Mazda 626 is a mid-size family car produced by the Japanese automaker Mazda from the late 1970s to the early 2000s, known for its practicality, reliability, and global popularity.
  • B. Mazda MX-6
    The Mazda MX-6 is a front-wheel-drive sport coupe produced by Mazda from the late 1980s to the late 1990s, known for its sleek styling and balanced performance.
  • C. Mazda SC
    Mazda SC was a Japanese company football club owned by Mazda that later evolved into the professional J.League team Sanfrecce Hiroshima.
  • D. Mazda6
    The Mazda6 is a mid-size family sedan known for its sporty handling, stylish design, and strong value in the mainstream car market.
  • E. Mazda3
    The Mazda3 is a popular compact car known for its sporty handling, stylish design, and well-appointed interior.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e9804e708190b15f5d38cac9c4c1 completed April 7, 2026, 11:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69d94af4ee6881909a36ee1a06a9d3e2 completed April 10, 2026, 7:09 p.m.
Created at: April 6, 2026, 12:02 p.m.