Triple
T26610640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American harness racing |
E667911
|
entity |
| Predicate | hasGaitRequirement |
P145939
|
FINISHED |
| Object | trot |
—
|
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: trot | Statement: [North American harness racing, hasGaitRequirement, trot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGaitRequirement Context triple: [North American harness racing, hasGaitRequirement, trot]
-
A.
hasPrimaryGait
Indicates that one entity is the main or characteristic type of gait (manner of walking or locomotion) exhibited by another entity.
-
B.
eligibleGait
chosen
Indicates that a particular gait meets the required criteria or conditions to be considered valid or acceptable for a given purpose.
-
C.
hasRacingGait
Indicates that an entity exhibits a specific style or pattern of movement characteristic of racing.
-
D.
isGaited
Indicates that an entity moves with a specific, often smooth or distinctive, pattern of walking or locomotion.
-
E.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:16 a.m.