Triple
T14106978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Topaz |
E339531
|
entity |
| Predicate | offeredTransmission |
P11928
|
FINISHED |
| Object | 5-speed 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: 5-speed manual transmission | Statement: [Mercury Topaz, offeredTransmission, 5-speed manual transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredTransmission Context triple: [Mercury Topaz, offeredTransmission, 5-speed 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.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
C.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
D.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
-
E.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600ada808190b92d67dc30f13d15 |
completed | April 14, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.