Triple
T33593936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford T3 platform |
E860505
|
entity |
| Predicate | productionSitePlanned |
P348
|
FINISHED |
| Object | BlueOval City |
—
|
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: BlueOval City | Statement: [Ford T3 platform, productionSitePlanned, BlueOval City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionSitePlanned Context triple: [Ford T3 platform, productionSitePlanned, BlueOval City]
-
A.
manufacturingSite
Indicates the location or facility where a product is or was manufactured.
-
B.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
C.
plannedFacility
chosen
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
D.
plannedProductionVersion
Indicates that a specific version of a product or item is scheduled or intended to be produced in the future.
-
E.
masterplannedBy
Indicates that an area or development project has been comprehensively designed or organized according to an overarching plan created by a specific planner or planning entity.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 1, 2026, 1:41 a.m.