Triple
T763053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldsmobile Ninety-Eight |
E16112
|
entity |
| Predicate | typicalTransmission |
P7413
|
FINISHED |
| Object | automatic 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: automatic transmission | Statement: [Oldsmobile Ninety-Eight, typicalTransmission, automatic transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTransmission Context triple: [Oldsmobile Ninety-Eight, typicalTransmission, automatic transmission]
-
A.
transmissionStandard
Indicates the communication or signal protocol used to transmit data or content between systems or devices.
-
B.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
C.
transmissionType
chosen
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
D.
broadcastNetworkTypical
Indicates that a given broadcast network is the one typically or commonly associated with airing the specified content or program.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6841f388190a6d08c3bf5c17fe4 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a506106081909ef97a679ff00a5a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.