Triple
T24976616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Superbe |
E625038
|
entity |
| Predicate | hasGearSystem |
P88077
|
FINISHED |
| Object | internal gear hub |
—
|
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: internal gear hub | Statement: [Raleigh Superbe, hasGearSystem, internal gear hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGearSystem Context triple: [Raleigh Superbe, hasGearSystem, internal gear hub]
-
A.
hasNumberOfGears
Indicates that an entity possesses a specified count of gears as a characteristic or component.
-
B.
gearSystemType
chosen
Indicates the specific configuration or category of gear mechanism used in a system or device.
-
C.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
D.
hasRunningGear
Indicates that an entity is equipped with or possesses running gear, such as the mechanical components that enable movement or operation.
-
E.
usesBeltSystem
Indicates that a subject employs a structured belt-ranking system (e.g., colored belts) to denote levels of skill, progress, or status.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:02 a.m.