Triple
T34603422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedlington |
E888526
|
entity |
| Predicate | hasDogBreedConnection |
P41121
|
FINISHED |
| Object | origin of Bedlington Terrier name |
—
|
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: origin of Bedlington Terrier name | Statement: [Bedlington, hasDogBreedConnection, origin of Bedlington Terrier name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDogBreedConnection Context triple: [Bedlington, hasDogBreedConnection, origin of Bedlington Terrier name]
-
A.
associatedAnimalBreed
chosen
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
B.
sameBreedAs
Indicates that two entities belong to the same breed or variety within a species.
-
C.
isRecognizedAsBreed
Indicates that an entity is officially acknowledged or accepted as a distinct breed within a particular classification or standard.
-
D.
belongsToBreedGroup
Indicates that an animal is classified as a member of a specific breed group.
-
E.
hasBreedRegistry
Indicates that an animal or breed is officially recorded or recognized in a specific breed registry or studbook.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 2:03 a.m.