Triple
T11419950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Softail |
E270592
|
entity |
| Predicate | hasStyling |
P1609
|
FINISHED |
| Object | classic hardtail look |
—
|
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: classic hardtail look | Statement: [Softail, hasStyling, classic hardtail look]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStyling Context triple: [Softail, hasStyling, classic hardtail look]
-
A.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasStructuralStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular architectural or structural design style.
-
C.
stylingEnables
Indicates that one entity provides or activates styling capabilities or visual formatting for another entity.
-
D.
selfStyling
Indicates that an entity independently chooses or creates its own style, appearance, or manner of presentation.
-
E.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
- 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.