Triple
T4437983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrogate |
E95697
|
entity |
| Predicate | racingSurfaceSpecialty |
P50583
|
FINISHED |
| Object | dirt |
—
|
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: dirt | Statement: [Arrogate, racingSurfaceSpecialty, dirt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingSurfaceSpecialty Context triple: [Arrogate, racingSurfaceSpecialty, dirt]
-
A.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
B.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
C.
ridingSpecialty
Indicates that one entity has a particular area of expertise or focus related to riding (e.g., a specific riding style, discipline, or type).
-
D.
competitionSurface
Indicates the type of surface or medium on which a competition or contest takes place.
-
E.
hasMotorRacingCircuit
Indicates that a location or entity possesses, contains, or is the site of a motor racing circuit.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558c75948190875a5fb10eac0597 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.