Triple
T11717018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Street Glide |
E278524
|
entity |
| Predicate | hasExhaustType |
P32744
|
FINISHED |
| Object | dual exhaust |
—
|
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: dual exhaust | Statement: [Harley-Davidson Street Glide, hasExhaustType, dual exhaust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhaustType Context triple: [Harley-Davidson Street Glide, hasExhaustType, dual exhaust]
-
A.
exhaustType
chosen
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
hasExtractionType
Indicates that one entity is associated with a specific method, category, or mode by which something is extracted from it or through it.
-
C.
hasTankType
Indicates that an entity is associated with, or classified by, a specific type or category of tank.
-
D.
hasSternType
Indicates that an entity (typically a vessel) possesses a specific type or design of stern.
-
E.
hasBoreType
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c10d988190842acd824135cf15 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.