Triple
T37268924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Fat Bob |
E924460
|
entity |
| Predicate | hasHeadlampConfiguration |
P59557
|
FINISHED |
| Object | dual headlamps |
—
|
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 headlamps | Statement: [Harley-Davidson Fat Bob, hasHeadlampConfiguration, dual headlamps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadlampConfiguration Context triple: [Harley-Davidson Fat Bob, hasHeadlampConfiguration, dual headlamps]
-
A.
headlightType
chosen
Indicates the specific kind or category of headlights that an entity is equipped with or uses.
-
B.
hasLumen
Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
-
C.
hasTorch
Indicates that one entity possesses or is currently holding a torch in relation to another context or entity.
-
D.
hasFrontFeature
Indicates that an entity possesses a specific characteristic, component, or attribute located on its front side.
-
E.
hasTorchRelay
Indicates that an event or entity includes or is associated with a torch relay as part of its activities or proceedings.
- 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_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:15 p.m.