Triple
T35307092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hexapoda |
E1019665
|
entity |
| Predicate | taxonomicRankBelow |
P31421
|
FINISHED |
| Object | Arthropoda |
—
|
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: Arthropoda | Statement: [Hexapoda, taxonomicRankBelow, Arthropoda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxonomicRankBelow Context triple: [Hexapoda, taxonomicRankBelow, Arthropoda]
-
A.
hasTaxonomicRankBelow
chosen
Indicates that one taxonomic rank is hierarchically lower (more specific) than another within a classification system.
-
B.
hasTaxonomicRankAbove
Indicates that one taxonomic rank is hierarchically higher (more inclusive) than another in a classification system.
-
C.
establishedTaxonomicRank
Indicates that one entity has formally defined or assigned the taxonomic rank or classification level of another entity within a biological taxonomy.
-
D.
taxonRank
Indicates the formal hierarchical rank (such as species, genus, family, etc.) that a given taxon occupies within a biological classification system.
-
E.
studiedTaxonRank
Indicates that an entity’s study or research activity is specifically focused on organisms at a particular taxonomic rank (e.g., species, genus, family).
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790522fbc81908a918eda08edd6e1 |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.