Triple
T26729537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Racecourse |
E673927
|
entity |
| Predicate | turfCourseDirection |
P76664
|
FINISHED |
| Object | left-handed |
—
|
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: left-handed | Statement: [Tokyo Racecourse, turfCourseDirection, left-handed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turfCourseDirection Context triple: [Tokyo Racecourse, turfCourseDirection, left-handed]
-
A.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
B.
turfCourseDistance
Indicates the distance over which an event or action occurs on a turf (grass) course.
-
C.
routeDirectionB
chosen
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
D.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618401d2481908b10199b30333192 |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:44 a.m.