Triple
T37268534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Fat Boy |
E924450
|
entity |
| Predicate | hasCustomizationOptions |
P139067
|
FINISHED |
| Object | factory accessories |
—
|
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: factory accessories | Statement: [Harley-Davidson Fat Boy, hasCustomizationOptions, factory accessories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomizationOptions Context triple: [Harley-Davidson Fat Boy, hasCustomizationOptions, factory accessories]
-
A.
customizableFeatures
chosen
Indicates that certain aspects or options of an entity can be modified or configured according to specific preferences or requirements.
-
B.
haveCustom
Indicates that one entity possesses, uses, or is associated with a non-standard or specially tailored version of another entity.
-
C.
hasCustomizationArea
Indicates that an entity includes or is associated with a specific area or section dedicated to customization or configuration.
-
D.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
E.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:15 p.m.