Triple
T16243358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trae Young |
E394306
|
entity |
| Predicate | shootingRange |
P122309
|
FINISHED |
| Object | beyond NBA three-point line |
—
|
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: beyond NBA three-point line | Statement: [Trae Young, shootingRange, beyond NBA three-point line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shootingRange Context triple: [Trae Young, shootingRange, beyond NBA three-point line]
-
A.
shootingDiscipline
Indicates the specific type or category of shooting activity or event in which an entity participates or is involved.
-
B.
shootingStyle
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
-
C.
shooter
Indicates that one entity performs a shooting action directed at another entity.
-
D.
flightScope
Indicates a relationship where the extent, range, or coverage of a flight (such as its route, duration, or operational limits) is specified or constrained.
-
E.
rifleHomeRange
Indicates the typical spatial area within which rifle-related activities or use are normally carried out.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24560060c8190ace4f4c0bd0d886d |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.