Triple
T24872687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darry Curtis |
E622476
|
entity |
| Predicate | athleticAbility |
P110098
|
FINISHED |
| Object | excellent football player |
—
|
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: excellent football player | Statement: [Darry Curtis, athleticAbility, excellent football player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athleticAbility Context triple: [Darry Curtis, athleticAbility, excellent football player]
-
A.
sportsSkill
chosen
Indicates that an entity possesses a particular ability, proficiency, or level of competence in performing a sport or sports-related activity.
-
B.
isAthletic
Indicates that an entity possesses physical fitness, strength, agility, or endurance characteristic of athletic ability.
-
C.
runningAbility
Indicates the capability or proficiency of an entity to run, typically in terms of speed, endurance, or effectiveness.
-
D.
hasAthleticLevel
Indicates the degree or category of athletic ability, fitness, or performance associated with an entity.
-
E.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:23 a.m.