Triple
T26387407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run and shoot offense |
E663317
|
entity |
| Predicate | ballDistribution |
P160484
|
FINISHED |
| Object | spreads targets among multiple receivers |
—
|
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: spreads targets among multiple receivers | Statement: [Run and shoot offense, ballDistribution, spreads targets among multiple receivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballDistribution Context triple: [Run and shoot offense, ballDistribution, spreads targets among multiple receivers]
-
A.
ballCount
Indicates the number of balls associated with a given entity or context.
-
B.
distributionFor
Indicates a relationship where one entity serves as the distribution, delivery, or dissemination mechanism for another entity.
-
C.
distributionBy
Indicates how something is allocated, arranged, or spread according to a specified criterion or grouping.
-
D.
classDistribution
Indicates how instances are proportionally or numerically distributed across different classes or categories within a dataset or grouping.
-
E.
ballType
Indicates the specific category or kind of ball associated with an entity.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bc2b288190ae10e6c27e5df786 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:23 p.m.