Triple
T20081695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southland Greyhound Park |
E500017
|
entity |
| Predicate | statusOfGreyhoundRacing |
P138639
|
FINISHED |
| Object | discontinued |
—
|
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: discontinued | Statement: [Southland Greyhound Park, statusOfGreyhoundRacing, discontinued]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfGreyhoundRacing Context triple: [Southland Greyhound Park, statusOfGreyhoundRacing, discontinued]
-
A.
raceStatus
Indicates the current state or progress of an entity’s participation in a race or competitive event.
-
B.
raceStatusHistory
Indicates the recorded sequence of status changes or states that a race has undergone over time.
-
C.
notableRaceStatus
Indicates that an entity holds a distinguished or significant status in the context of a particular race or racing event.
-
D.
raceSurfaceHistory
Indicates the type of surface on which an entity has raced in the past, capturing its historical race-surface conditions.
-
E.
racecourseOpened
Indicates that a racecourse began operating or was officially opened on a specified date or at a specified time.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e665588a9c8190886b693b13a215a8 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:41 p.m.