Triple
T30504185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakraborty & Mohan, 1981 |
E776220
|
entity |
| Predicate | describedGenus |
P91808
|
FINISHED |
| Object | Biswamoyopterus |
—
|
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: Biswamoyopterus | Statement: [Chakraborty & Mohan, 1981, describedGenus, Biswamoyopterus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedGenus Context triple: [Chakraborty & Mohan, 1981, describedGenus, Biswamoyopterus]
-
A.
describedTaxon
Indicates that an entity (such as a publication or description) formally describes or establishes the referenced taxon.
-
B.
describedAsSpecies
Indicates that one entity is characterized or identified as a particular species in relation to another entity.
-
C.
firstDescribedAsGenusBy
chosen
Indicates that one entity was the first to formally describe another entity as a genus in a taxonomic or scientific context.
-
D.
speciesDescription
Indicates a textual description that characterizes or explains the features, traits, or nature of a species.
-
E.
describedAsSmallGenus
Indicates that something is characterized or classified as a small genus in a taxonomic or categorical 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:15 p.m.