Triple
T66518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldsmobile Delmont 88 |
E1326
|
entity |
| Predicate | transmission |
P4163
|
FINISHED |
| Object | 3-speed manual |
—
|
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: 3-speed manual | Statement: [Oldsmobile Delmont 88, transmission, 3-speed manual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmission Context triple: [Oldsmobile Delmont 88, transmission, 3-speed manual]
-
A.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
B.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
C.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
-
D.
publicTransit
Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
-
E.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2509b5a088190bb9d2b650aeb8bca |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ea749788190bc17865171ff909a |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a2509a1c088190b4afa3045455709a |
completed | Feb. 28, 2026, 2:19 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.