Triple
T22360685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Racking Horse |
E552770
|
entity |
| Predicate | hasGaitType |
P23273
|
FINISHED |
| Object | single-foot gait |
—
|
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: single-foot gait | Statement: [Racking Horse, hasGaitType, single-foot gait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGaitType Context triple: [Racking Horse, hasGaitType, single-foot gait]
-
A.
hasRacingGait
Indicates that an entity exhibits a specific style or pattern of movement characteristic of racing.
-
B.
eligibleGait
Indicates that a particular gait meets the required criteria or conditions to be considered valid or acceptable for a given purpose.
-
C.
hasLegType
Indicates that an entity possesses a specific type or category of legs.
-
D.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
E.
hasMovementType
chosen
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d3852c819082518851568e1b51 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.