Triple
T37252164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poecilia reticulata |
E924022
|
entity |
| Predicate | breedingEase |
P189380
|
FINISHED |
| Object | easy to breed in captivity |
—
|
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: easy to breed in captivity | Statement: [Poecilia reticulata, breedingEase, easy to breed in captivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingEase Context triple: [Poecilia reticulata, breedingEase, easy to breed in captivity]
-
A.
breedingAssociation
Indicates a relationship where entities are associated for the purpose of breeding or reproduction.
-
B.
breedingCenter
Indicates a relationship where an entity serves as a facility or location dedicated to breeding or reproducing organisms.
-
C.
breedingGoal
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
D.
sireOfSires
Indicates that an entity is the male ancestor (a sire) of other sires, i.e., it fathers individuals who themselves become sires.
-
E.
breedingTrait
Indicates that an entity possesses a heritable characteristic that is relevant or targeted in a breeding process or program.
- F. None of above. chosen
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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:15 p.m.