Triple
T16745162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiorenzo Magni |
E406932
|
entity |
| Predicate | usedHandlebarStrapTo |
P124473
|
FINISHED |
| Object | support injured shoulder while climbing |
—
|
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: support injured shoulder while climbing | Statement: [Fiorenzo Magni, usedHandlebarStrapTo, support injured shoulder while climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHandlebarStrapTo Context triple: [Fiorenzo Magni, usedHandlebarStrapTo, support injured shoulder while climbing]
-
A.
handlebarType
Indicates the specific style or design of handlebars associated with an entity.
-
B.
hasHandlebarFairing
Indicates that an object is equipped with a fairing specifically mounted on or integrated into its handlebars.
-
C.
hasStrapType
Indicates that an item is associated with or equipped with a specific type or style of strap.
-
D.
usedToHandle
Indicates that one entity previously managed, processed, or dealt with another entity as part of its function or role.
-
E.
hasBoltHandle
Indicates that one entity is equipped with or includes a bolt-style handle associated with another entity.
- F. None of above. chosen
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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa223aa88190a3c1805ece7317e2 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.