Triple
T38045187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black and Tan Coonhound |
E949598
|
entity |
| Predicate | ancestralBreed |
P186857
|
FINISHED |
| Object | Bloodhound |
—
|
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: Bloodhound | Statement: [Black and Tan Coonhound, ancestralBreed, Bloodhound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralBreed Context triple: [Black and Tan Coonhound, ancestralBreed, Bloodhound]
-
A.
breedsFrom
chosen
Indicates that one organism or entity is produced, derived, or propagated from another through breeding or reproductive processes.
-
B.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
C.
recognizedAsSeparateBreedFrom
Indicates that one animal population or type is officially acknowledged as a distinct breed, separate from another.
-
D.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
E.
originBreeds
Indicates that one entity is the place or source from which another entity (typically a breed or type) originates or was developed.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.