Triple
T2199383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Fox platform (third generation) |
E50452
|
entity |
| Predicate | transmissionCompatibility |
P11928
|
FINISHED |
| Object | manual transmission |
—
|
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: manual transmission | Statement: [Ford Fox platform (third generation), transmissionCompatibility, manual transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionCompatibility Context triple: [Ford Fox platform (third generation), transmissionCompatibility, manual transmission]
-
A.
transmissionTypeSupported
chosen
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
B.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
C.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
D.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.