Triple
T24976555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Sports |
E625037
|
entity |
| Predicate | gearSystem |
P88077
|
FINISHED |
| Object | Sturmey-Archer 3-speed hub |
E1658298
|
NE 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: Sturmey-Archer 3-speed hub | Statement: [Raleigh Sports, gearSystem, Sturmey-Archer 3-speed hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearSystem Context triple: [Raleigh Sports, gearSystem, Sturmey-Archer 3-speed hub]
-
A.
gearSystemType
chosen
Indicates the specific configuration or category of gear mechanism used in a system or device.
-
B.
gear
Indicates that one entity functions as a gear or toothed mechanical component that transmits motion or force to another entity.
-
C.
clockMechanism
Indicates that one entity functions as the internal mechanism or movement that drives the operation of a clock.
-
D.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
E.
gearboxLocation
Indicates the spatial position or placement of a gearbox relative to another object or reference frame.
- F. None of above.
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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1048a55b5081909691590148f8154f |
completed | May 22, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:02 a.m.