Triple
T26697532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan D'Antoni |
E673062
|
entity |
| Predicate | preferredShotSelection |
P161129
|
FINISHED |
| Object | three-point field goals |
—
|
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: three-point field goals | Statement: [Dan D'Antoni, preferredShotSelection, three-point field goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredShotSelection Context triple: [Dan D'Antoni, preferredShotSelection, three-point field goals]
-
A.
decisiveShotDescription
Indicates that an action or event constitutes the critical or game-changing shot that determines the final outcome.
-
B.
givesFirstPickTo
Indicates that one entity grants another entity the right to choose first among available options.
-
C.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
D.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
primaryShooter
Indicates that the subject is the main individual responsible for firing a weapon in the referenced event or context.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177c7ddc8190b6c96e97be69030d |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:29 a.m.