Triple
T18335778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry Scott |
E439265
|
entity |
| Predicate | hasSignatureExercise |
P131414
|
FINISHED |
| Object | Scott curl |
—
|
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: Scott curl | Statement: [Larry Scott, hasSignatureExercise, Scott curl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureExercise Context triple: [Larry Scott, hasSignatureExercise, Scott curl]
-
A.
hasSignatureWorkFeature
Indicates that an entity possesses a distinctive characteristic or element that defines or exemplifies its signature work.
-
B.
hasSignatureMechanic
Indicates that an entity (such as a game, character, or system) possesses a distinctive, defining mechanic or feature that is uniquely characteristic of it.
-
C.
hasSignaturePerformanceBy
Indicates that something features a standout or defining performance delivered by a particular performer.
-
D.
hasSignatureWorkStatus
Indicates that an entity has a particular status or state assigned to its designated signature or primary work.
-
E.
hasExerciseType
Indicates that an exercise or workout is associated with a specific type or category of physical activity.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecd759481909703ed2d0d68199f |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.