Triple
T36702631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heterandria formosa |
E906269
|
entity |
| Predicate | broodCharacteristic |
P40326
|
FINISHED |
| Object | superfetation |
—
|
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: superfetation | Statement: [Heterandria formosa, broodCharacteristic, superfetation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broodCharacteristic Context triple: [Heterandria formosa, broodCharacteristic, superfetation]
-
A.
broodCare
Indicates that an entity provides care, protection, or nurturing to its eggs or offspring during early developmental stages.
-
B.
breedingTrait
Indicates that an entity possesses a heritable characteristic that is relevant or targeted in a breeding process or program.
-
C.
brothCharacteristic
Indicates that one entity specifies a quality, feature, or attribute of a broth associated with another entity.
-
D.
biologicalCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
E.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7ee28c88190ad3f7adabd4650fc |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.