Triple

T17221750
Position Surface form Disambiguated ID Type / Status
Subject Technomyrmex E418001 entity
Predicate typeSpecies P7381 FINISHED
Object Technomyrmex albipes 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: Technomyrmex albipes | Statement: [Technomyrmex, typeSpecies, Technomyrmex albipes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Technomyrmex albipes
Context triple: [Technomyrmex, typeSpecies, Technomyrmex albipes]
  • A. Technomyrmex chosen
    Technomyrmex is a genus of small, often invasive dolichoderine ants widely distributed in tropical and subtropical regions.
  • B. Nebothriomyrmex
    Nebothriomyrmex is a genus of ants within the subfamily Dolichoderinae, known from the Neotropical region.
  • C. Leptomyrmex
    Leptomyrmex is a genus of distinctive, long-legged ants commonly known as “spider ants,” native primarily to Australia and nearby regions.
  • D. Ctenomyrmex
    Ctenomyrmex is a genus of ants within the subfamily Dolichoderinae, known from tropical regions and characterized by their arboreal nesting habits.
  • E. Bothriomyrmex
    Bothriomyrmex is a genus of ants known for its socially parasitic behavior, particularly its habit of enslaving or exploiting other ant species.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dde78f881908b03105fa0298ae2 completed April 19, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:38 a.m.