Triple
T11537840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smooth Collie |
E273593
|
entity |
| Predicate | bredFor |
P32409
|
FINISHED |
| Object | herding sheep |
—
|
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: herding sheep | Statement: [Smooth Collie, bredFor, herding sheep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bredFor Context triple: [Smooth Collie, bredFor, herding sheep]
-
A.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
B.
breedingGoal
chosen
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
C.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
D.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
-
E.
breeder
Indicates that an entity is responsible for producing, raising, or propagating another entity, typically through controlled reproduction.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839cdf688190ae75c0e6fece8e33 |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.