Triple
T23590138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trakehnen |
E582452
|
entity |
| Predicate | associatedBreedRegistry |
P59524
|
FINISHED |
| Object | Trakehner Verband |
—
|
NE NERFINISHED |
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: Trakehner Verband | Statement: [Trakehnen, associatedBreedRegistry, Trakehner Verband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBreedRegistry Context triple: [Trakehnen, associatedBreedRegistry, Trakehner Verband]
-
A.
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.
-
B.
hasBreedRegistry
chosen
Indicates that an animal or breed is officially recorded or recognized in a specific breed registry or studbook.
-
C.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
D.
breedingAssociation
Indicates a relationship where entities are associated for the purpose of breeding or reproduction.
-
E.
recognizedAsSeparateBreedFrom
Indicates that one animal population or type is officially acknowledged as a distinct breed, separate from another.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03484e4819093d5c14c891f7744 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.