Triple
T19450756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakout |
E486606
|
entity |
| Predicate | ballBehavior |
P135947
|
FINISHED |
| Object | angle of reflection depends on where ball hits paddle |
—
|
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: angle of reflection depends on where ball hits paddle | Statement: [Breakout, ballBehavior, angle of reflection depends on where ball hits paddle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballBehavior Context triple: [Breakout, ballBehavior, angle of reflection depends on where ball hits paddle]
-
A.
ballDirection
Indicates the direction in which a ball is or was moving relative to a reference point or frame.
-
B.
ballReboundPlay
Indicates a play in which the ball bounces or rebounds off a surface or player and continues in active play.
-
C.
ballMustExit
Indicates that the ball is required to leave or move out of a specified area, state, or context.
-
D.
ballType
Indicates the specific category or kind of ball associated with an entity.
-
E.
ballCondition
Indicates the specific state or status a ball is in, such as its physical condition, readiness for use, or compliance with required standards.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.