Triple
T12502148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Sussex |
E298852
|
entity |
| Predicate | breedingFocusTrait |
P103508
|
FINISHED |
| Object | consistent lacing |
—
|
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: consistent lacing | Statement: [Silver Sussex, breedingFocusTrait, consistent lacing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingFocusTrait Context triple: [Silver Sussex, breedingFocusTrait, consistent lacing]
-
A.
breedingTrait
chosen
Indicates that an entity possesses a heritable characteristic that is relevant or targeted in a breeding process or program.
-
B.
breedingGoal
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
C.
contributesTraitInCrossbreeding
Indicates that a particular parent organism provides or passes on a specific trait to the offspring resulting from a crossbreeding event.
-
D.
domesticationTrait
Indicates that an entity possesses a characteristic or feature that contributes to or results from its domestication by another species.
-
E.
breedingMethod
Indicates the technique or process by which organisms are bred or reproduced.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.