Triple
T315618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT800 |
E7698
|
entity |
| Predicate | transmissionTypeSupported |
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: [GMT800, transmissionTypeSupported, manual transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionTypeSupported Context triple: [GMT800, transmissionTypeSupported, manual transmission]
-
A.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
B.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
D.
canExpress
Indicates that an entity has the ability or capacity to convey, articulate, or communicate something (such as an idea, emotion, or property).
-
E.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
- F. None of above. chosen
Provenance (4 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.