Triple
T30728929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monmouth Park Racetrack |
E782360
|
entity |
| Predicate | hasTurfCourseLength |
P57551
|
FINISHED |
| Object | 7 furlongs |
—
|
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: 7 furlongs | Statement: [Monmouth Park Racetrack, hasTurfCourseLength, 7 furlongs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurfCourseLength Context triple: [Monmouth Park Racetrack, hasTurfCourseLength, 7 furlongs]
-
A.
golfCourseLength
Indicates the measured distance or extent of a golf course, typically from tee to hole or across the full course layout.
-
B.
hasOuterTurfCourse
Indicates that a location or facility includes an outer turf (grass) course as part of its layout or structure.
-
C.
hasInnerTurfCourse
Indicates that something (typically a race track or stadium) possesses an inner turf course located within its main track or field.
-
D.
turfCourseDistance
chosen
Indicates the distance over which an event or action occurs on a turf (grass) course.
-
E.
hasYardage
Indicates that something possesses or is associated with a specific measured distance or length, typically expressed in yards.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee186508190894808b23be1d88d |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:37 p.m.