Triple
T8779258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter the Ridgeback |
E208681
|
entity |
| Predicate | hasBreed |
P41121
|
FINISHED |
| Object | ridgeback |
—
|
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: ridgeback | Statement: [Hunter the Ridgeback, hasBreed, ridgeback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreed Context triple: [Hunter the Ridgeback, hasBreed, ridgeback]
-
A.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
B.
associatedAnimalBreed
chosen
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
C.
hasBreedRegistry
Indicates that an animal or breed is officially recorded or recognized in a specific breed registry or studbook.
-
D.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
-
E.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f531bd481909d877dadf9b6e9fb |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.