Triple
T37920065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redbone Coonhound |
E945927
|
entity |
| Predicate | ancestralBreeds |
P186857
|
FINISHED |
| Object | red foxhounds |
—
|
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: red foxhounds | Statement: [Redbone Coonhound, ancestralBreeds, red foxhounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralBreeds Context triple: [Redbone Coonhound, ancestralBreeds, red foxhounds]
-
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.
originBreeds
Indicates that one entity is the place or source from which another entity (typically a breed or type) originates or was developed.
-
D.
hasTraditionalAnimalBreed
Indicates that an entity is associated with or possesses an animal that belongs to a recognized traditional breed.
-
E.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.