Triple
T22360673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Walking Horse |
E552769
|
entity |
| Predicate | hasShowDivision |
P147900
|
FINISHED |
| Object | flat-shod division |
—
|
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: flat-shod division | Statement: [Tennessee Walking Horse, hasShowDivision, flat-shod division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShowDivision Context triple: [Tennessee Walking Horse, hasShowDivision, flat-shod division]
-
A.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
B.
hasDivisionCode
Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
-
C.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
D.
hasDivisionRule
Indicates that one entity is governed, organized, or separated according to a specified rule or method of division defined by another entity.
-
E.
hasDivisionNames
Indicates that an entity is associated with one or more names of its internal divisions or subunits.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.