Triple
T22402128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curva B |
E553785
|
entity |
| Predicate | isEndStandRelativeToPitch |
P148024
|
FINISHED |
| Object | behind one of the 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: behind one of the goals | Statement: [Curva B, isEndStandRelativeToPitch, behind one of the goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndStandRelativeToPitch Context triple: [Curva B, isEndStandRelativeToPitch, behind one of the goals]
-
A.
isEndStand
Indicates that something functions as the final or terminating stand, station, or stopping point in a sequence or route.
-
B.
isFinishLineOf
Indicates that something serves as the finish line or endpoint for a particular event, race, or process.
-
C.
hasPitchType
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
D.
isBowlingEndAt
Indicates that a specific location or point on a cricket field serves as a designated bowling end for delivering the ball.
-
E.
pitchConvertedTo
Indicates that one pitch has been transformed or translated into another pitch or pitch representation.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b4a96c8190838f5dda21c4d853 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.