Triple
T29904359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazda Motor Corporation |
E759494
|
entity |
| Predicate | usedFordPlatformsFor |
P180639
|
FINISHED |
| Object | Mazda B-Series pickup (North America) |
—
|
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 B-Series pickup (North America) | Statement: [Mazda Motor Corporation, usedFordPlatformsFor, Mazda B-Series pickup (North America)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFordPlatformsFor Context triple: [Mazda Motor Corporation, usedFordPlatformsFor, Mazda B-Series pickup (North America)]
-
A.
usedByPlatform
Indicates that something (such as a tool, component, or resource) is utilized or employed by a particular platform.
-
B.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
C.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
D.
usedOnVehicleFamily
Indicates that something is designed or intended to be used on a particular family or category of vehicles.
-
E.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 29, 2026, 6:07 p.m.