Triple
T29526981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakville Assembly Complex |
E749093
|
entity |
| Predicate | hasNotableFormerProduct |
P25918
|
FINISHED |
| Object | Ford Freestar |
—
|
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: Ford Freestar | Statement: [Oakville Assembly Complex, hasNotableFormerProduct, Ford Freestar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFormerProduct Context triple: [Oakville Assembly Complex, hasNotableFormerProduct, Ford Freestar]
-
A.
formerProduct
chosen
Indicates that an entity was previously a product of another entity but is no longer in that role or status.
-
B.
hasNotableSuccessorCompany
Indicates that an entity is followed by another company recognized as a particularly important or prominent successor.
-
C.
formerlyUsedBy
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
D.
previousBrandProduced
Indicates that a brand which previously existed or operated before the current one was responsible for producing the specified product or item.
-
E.
hasFormerBrandOwner
Indicates that an entity was previously the owner of a particular brand, but no longer holds that ownership.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: April 28, 2026, 4:47 p.m.