Triple
T22598967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Catch |
E574759
|
entity |
| Predicate | passDirection |
P51219
|
FINISHED |
| Object | back of the end zone |
—
|
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: back of the end zone | Statement: [The Catch, passDirection, back of the end zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passDirection Context triple: [The Catch, passDirection, back of the end zone]
-
A.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
B.
crossingDirection
chosen
Indicates the direction in which one entity moves or passes across another reference point, boundary, or path.
-
C.
transmissionDirection
Indicates the direction in which something is transmitted or passed from one entity to another.
-
D.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
E.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
- F. None of above.
Provenance (3 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626b5f5481909a104088d1c96720 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.