Triple
T13630387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Glove |
E325697
|
entity |
| Predicate | appliesToSkill |
P6204
|
FINISHED |
| Object | on-ball defense |
—
|
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: on-ball defense | Statement: [The Glove, appliesToSkill, on-ball defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToSkill Context triple: [The Glove, appliesToSkill, on-ball defense]
-
A.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
B.
requiresSkill
chosen
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
C.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
D.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
E.
validatesSkill
Indicates that one entity confirms or verifies the authenticity, correctness, or adequacy of another entity’s skill or competency.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.