Triple
T24581212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ball |
E608254
|
entity |
| Predicate | movementDetermines |
P156425
|
FINISHED |
| Object | offside decisions |
—
|
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: offside decisions | Statement: [The Ball, movementDetermines, offside decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementDetermines Context triple: [The Ball, movementDetermines, offside decisions]
-
A.
movementDepicted
Indicates that some form of motion or change in position is visually represented or illustrated.
-
B.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
C.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
D.
moves
Indicates that an entity changes its position or location over time, typically from one place to another.
-
E.
movementRole
Indicates the specific function or capacity an entity has within a movement or motion-related activity (e.g., mover, path, source, or goal).
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a982db00819081038adce05c0b52 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:29 a.m.