Triple
T37919912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hound Group |
E945924
|
entity |
| Predicate | containsBreed |
P86874
|
FINISHED |
| Object | Beagle |
E2188896
|
NE 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: Beagle | Statement: [Hound Group, containsBreed, Beagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBreed Context triple: [Hound Group, containsBreed, Beagle]
-
A.
hasVarietyWithinBreed
Indicates that within a given breed, there exist distinct varieties or subtypes that are recognized as variations of that same breed.
-
B.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
C.
belongsToBreedGroup
chosen
Indicates that an animal is classified as a member of a specific breed group.
-
D.
breedsFrom
Indicates that one organism or entity is produced, derived, or propagated from another through breeding or reproductive processes.
-
E.
hasTypicalBreed
Indicates that an entity (such as an animal or pet) is associated with a breed that is considered standard or characteristic for its kind.
- F. None of above.
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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01d339feac8190a3de56b24db67163 |
completed | May 11, 2026, 1:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cd2e2ec819094f052f317c489c0 |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_6a01d2bc1f408190a04869f95e6941ee |
completed | May 11, 2026, 12:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.