Triple
T37268886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Wide Glide |
E924459
|
entity |
| Predicate | frameFamily |
P187977
|
FINISHED |
| Object | Dyna |
—
|
NE NERFINISHED |
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: Dyna | Statement: [Harley-Davidson Wide Glide, frameFamily, Dyna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameFamily Context triple: [Harley-Davidson Wide Glide, frameFamily, Dyna]
-
A.
frameworkFamily
Indicates that one framework belongs to the same overarching family or lineage as another framework, typically sharing core principles, architecture, or origin.
-
B.
frame
Indicates placing or presenting something within a particular context, structure, or perspective that shapes how it is interpreted.
-
C.
frameType
Indicates the specific structural or categorical kind of frame associated with an entity or relation.
-
D.
framesAs
Indicates how one entity presents, characterizes, or interprets another entity or situation in a particular light or context.
-
E.
frameShape
Indicates that one entity has the specified geometric or structural shape of a frame in relation to another entity.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:15 p.m.