Triple
T24659569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron Holiday |
E610499
|
entity |
| Predicate | isFromBasketballFamily |
P156926
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aaron Holiday, isFromBasketballFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromBasketballFamily Context triple: [Aaron Holiday, isFromBasketballFamily, true]
-
A.
usesBasketball
Indicates that one entity makes use of or engages with basketball, typically as equipment or in the context of playing the sport.
-
B.
hasBasketballLevel
Indicates that an entity possesses a specified level of skill, proficiency, or ranking in basketball.
-
C.
playedBasketballFor
Indicates that one entity was a member of and competed for another entity’s basketball team.
-
D.
playsHomeBasketballAt
Indicates that a person or team plays their home basketball games at a specified venue or location.
-
E.
representsInBasketball
Indicates that one entity serves as an official representative (such as an agent, delegate, or spokesperson) for another entity specifically in the context of basketball.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:34 a.m.