Triple
T37579784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Daishoten |
E934922
|
entity |
| Predicate | raceSurfaceUse |
P50583
|
FINISHED |
| Object | primarily for dirt specialists |
—
|
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: primarily for dirt specialists | Statement: [Tokyo Daishoten, raceSurfaceUse, primarily for dirt specialists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceSurfaceUse Context triple: [Tokyo Daishoten, raceSurfaceUse, primarily for dirt specialists]
-
A.
racecourseUsed
Indicates that a particular racecourse is utilized or employed for a given event, activity, or purpose.
-
B.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
C.
raceSurfaceHistory
Indicates the type of surface on which an entity has raced in the past, capturing its historical race-surface conditions.
-
D.
racewayBuiltOn
Indicates that a raceway (such as a track or circuit) is constructed on or occupies the physical area of a specified underlying surface or location.
-
E.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.