Triple
T22360713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Racking Horse |
E552770
|
entity |
| Predicate | isRecognizedAsBreed |
P147903
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Racking Horse, isRecognizedAsBreed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecognizedAsBreed Context triple: [Racking Horse, isRecognizedAsBreed, true]
-
A.
recognizedAsSeparateBreedFrom
Indicates that one animal population or type is officially acknowledged as a distinct breed, separate from another.
-
B.
hasBreedRegistry
Indicates that an animal or breed is officially recorded or recognized in a specific breed registry or studbook.
-
C.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
D.
governingBreedRegistry
Indicates that an entity serves as the official breed registry authority responsible for recognizing, recording, and regulating a particular breed or group of breeds.
-
E.
madeFromBreed
Indicates that something is produced or derived using a particular breed as its source or primary constituent.
- 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.