Triple
T29904361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Motor Company |
E759494
|
entity |
| Predicate | sharedManufacturingFacilitiesWith |
P71121
|
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, sharedManufacturingFacilitiesWith, Mazda Motor Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedManufacturingFacilitiesWith Context triple: [Ford Motor Company, sharedManufacturingFacilitiesWith, Mazda Motor Corporation]
-
A.
hasProductionFacilitiesIn
Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
-
B.
manufacturingSite
Indicates the location or facility where a product is or was manufactured.
-
C.
sharesFacilityWith
chosen
Indicates that two entities use or have access to the same physical facility or location.
-
D.
sharesManufacturerWith
Indicates that two entities are produced by the same manufacturer.
-
E.
haveSharedInfrastructure
Indicates that two or more entities use or depend on the same underlying physical or virtual infrastructure resources.
- 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_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 6:07 p.m.