Triple
T33675802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford T6 platform |
E862755
|
entity |
| Predicate | supportsBodyStyles |
P42045
|
FINISHED |
| Object | double cab pickup |
—
|
LITERAL FINISHED |
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: double cab pickup | Statement: [Ford T6 platform, supportsBodyStyles, double cab pickup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBodyStyles Context triple: [Ford T6 platform, supportsBodyStyles, double cab pickup]
-
A.
supportsBody
Indicates that one entity physically or structurally holds up, bears the weight of, or provides foundational stability for another entity’s body.
-
B.
supportsBodyType
chosen
Indicates that one entity is compatible with, designed for, or can accommodate a specified body type.
-
C.
associatedWithBodyStyles
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
D.
offersBodyStyle
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
E.
appliesToBodyType
Indicates that something (such as a rule, feature, or specification) is relevant or applicable to a particular body type.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:43 a.m.