Triple
T29904354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Motor Company |
E759494
|
entity |
| Predicate | sharedPickupTruckPlatformWith |
P174320
|
FINISHED |
| Object | Mazda Motor Corporation |
—
|
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 Motor Corporation | Statement: [Ford Motor Company, sharedPickupTruckPlatformWith, Mazda Motor Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedPickupTruckPlatformWith Context triple: [Ford Motor Company, sharedPickupTruckPlatformWith, Mazda Motor Corporation]
-
A.
typicalPickupType
Indicates the usual or standard method by which an item or order is collected or picked up.
-
B.
sharesChassisWith
chosen
Indicates that two entities are built on the same underlying structural platform or frame.
-
C.
sharesTrunkWith
Indicates that two entities have a common trunk or main stem from which they both extend or branch.
-
D.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
E.
typicalPickupConfiguration
Indicates the usual or standard arrangement or setup used for picking up or collecting something in a given context.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 6:07 p.m.