Triple
T26826503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | telyn |
E675387
|
entity |
| Predicate | hasTuningMechanism |
P134343
|
FINISHED |
| Object | pedals |
—
|
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: pedals | Statement: [telyn, hasTuningMechanism, pedals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTuningMechanism Context triple: [telyn, hasTuningMechanism, pedals]
-
A.
tuningMachines
Indicates a relationship where an instrument or device is equipped with or associated with specific tuning machines used to adjust string tension.
-
B.
hasMechanicalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
C.
tuningType
Indicates the specific method or configuration by which something is adjusted or calibrated to achieve a desired performance or behavior.
-
D.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
tuningMethod
Indicates the method or approach used to adjust or optimize something’s parameters or performance.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 4:58 a.m.