Triple
T37437592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poecilia formosa |
E930320
|
entity |
| Predicate | requiresSpermFrom |
P157583
|
FINISHED |
| Object | Poecilia latipinna |
—
|
NE NERFINISHED |
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: Poecilia latipinna | Statement: [Poecilia formosa, requiresSpermFrom, Poecilia latipinna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSpermFrom Context triple: [Poecilia formosa, requiresSpermFrom, Poecilia latipinna]
-
A.
fertilizationRequires
Indicates that a fertilization event can only occur if a specified condition, resource, or process is present or has taken place.
-
B.
providedSpermDonorFor
Indicates that one entity served as the sperm donor used for another entity’s conception or reproductive process.
-
C.
reproductionConstraint
Indicates a limitation, condition, or rule that restricts or governs how reproduction or generative processes may occur between entities.
-
D.
requiresItemForBreeding
Indicates that one entity must have or use a specific item in order for a breeding action or process with another entity to occur.
-
E.
breedingRequirement
chosen
Indicates the conditions or factors that must be satisfied for successful breeding to occur between entities.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:17 p.m.