Triple
T11363514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Chimneys Farm |
E269144
|
entity |
| Predicate | hasBreedingProgramType |
P83041
|
FINISHED |
| Object | commercial breeding program |
—
|
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: commercial breeding program | Statement: [Three Chimneys Farm, hasBreedingProgramType, commercial breeding program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreedingProgramType Context triple: [Three Chimneys Farm, hasBreedingProgramType, commercial breeding program]
-
A.
hasBreedingProgram
Indicates that an entity operates, participates in, or maintains an organized program for breeding organisms (such as animals or plants).
-
B.
hasBreedingCode
Indicates that an entity is associated with a specific code representing its breeding status, behavior, or category.
-
C.
breedingMethod
Indicates the technique or process by which organisms are bred or reproduced.
-
D.
breedingInstitutionType
chosen
Indicates the type or category of institution responsible for breeding organisms or animals.
-
E.
breedingGoal
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.