Triple
T11420069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyna |
E270594
|
entity |
| Predicate | hasHandlebarStyle |
P88228
|
FINISHED |
| Object | varies by model including drag bars and ape hangers |
—
|
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: varies by model including drag bars and ape hangers | Statement: [Dyna, hasHandlebarStyle, varies by model including drag bars and ape hangers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHandlebarStyle Context triple: [Dyna, hasHandlebarStyle, varies by model including drag bars and ape hangers]
-
A.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
handlebarType
chosen
Indicates the specific style or design of handlebars associated with an entity.
-
C.
hasContractStyle
Indicates that one entity is associated with or characterized by a particular contract style or contractual format.
-
D.
hasStationStyle
Indicates that one entity (typically a station) possesses or is characterized by a particular architectural or design style.
-
E.
hasHandle
Indicates that one entity possesses or is equipped with a handle used for holding, carrying, or operating it.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b20ce08190befc98379b879985 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.