Triple
T22558560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ponty End |
E557751
|
entity |
| Predicate | isEndOfPitch |
P148657
|
FINISHED |
| Object | one goal end at Oakwell Stadium |
—
|
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: one goal end at Oakwell Stadium | Statement: [The Ponty End, isEndOfPitch, one goal end at Oakwell Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndOfPitch Context triple: [The Ponty End, isEndOfPitch, one goal end at Oakwell Stadium]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
hasPitchLength
Indicates that an entity (such as a field or pitch) is associated with a specific measurement of its length.
-
C.
isFinishLineOf
Indicates that something serves as the finish line or endpoint for a particular event, race, or process.
-
D.
hasPitchType
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
E.
hasFinalSyllable
Indicates that one entity possesses or ends with a specific final syllable represented by the other 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7be004819083c1c8c0e7863d6f |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:52 p.m.