Triple
T37544264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryson DeChambeau |
E933413
|
entity |
| Predicate | usesEquipmentFeature |
P101141
|
FINISHED |
| Object | single-length irons |
—
|
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: single-length irons | Statement: [Bryson DeChambeau, usesEquipmentFeature, single-length irons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEquipmentFeature Context triple: [Bryson DeChambeau, usesEquipmentFeature, single-length irons]
-
A.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
B.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
hasElectronicsFeature
Indicates that an entity possesses or is characterized by a specific electronic-related feature or capability.
-
D.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
E.
typeOfEquipmentUsed
chosen
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.