Triple
T28888512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramphocoris |
E732631
|
entity |
| Predicate | isInfrataxonOf |
P101474
|
FINISHED |
| Object | Passeriformes |
—
|
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: Passeriformes | Statement: [Ramphocoris, isInfrataxonOf, Passeriformes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInfrataxonOf Context triple: [Ramphocoris, isInfrataxonOf, Passeriformes]
-
A.
belongsToInfraorder
chosen
Indicates that one entity is taxonomically classified as a member of the infraorder specified by the other entity.
-
B.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
C.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
D.
infraphylum
Indicates a taxonomic relationship where one entity is classified as an infraphylum, a rank directly below a subphylum and above a superclass, within the biological hierarchy of another entity.
-
E.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 7:53 a.m.