Triple
T31119213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brevoortia |
E793177
|
entity |
| Predicate | genusContainsSpecies |
P9413
|
FINISHED |
| Object | Brevoortia tyrannus |
—
|
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: Brevoortia tyrannus | Statement: [Brevoortia, genusContainsSpecies, Brevoortia tyrannus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genusContainsSpecies Context triple: [Brevoortia, genusContainsSpecies, Brevoortia tyrannus]
-
A.
genusIncludes
chosen
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
-
B.
isTypeSpeciesOfGenus
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a particular genus.
-
C.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
D.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
E.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.