Triple

T11190063
Position Surface form Disambiguated ID Type / Status
Subject ToMMo E264772 entity
Predicate hasAbbreviation P43 FINISHED
Object ToMMo E264772 NE FINISHED

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: ToMMo | Statement: [ToMMo, hasAbbreviation, ToMMo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ToMMo
Context triple: [ToMMo, hasAbbreviation, ToMMo]
  • A. ToMMo chosen
    ToMMo is a Japanese research organization focused on large-scale biobanking and genomic medicine, based at the Tohoku University-affiliated Tohoku Medical Megabank Organization.
  • B. TMOK
    TMOK is the Turkish National Olympic Committee responsible for organizing Turkey's participation in the Olympic Games and promoting the Olympic movement in the country.
  • C. MMTO
    MMTO is the ICAO airport code for Toluca International Airport, a commercial and cargo airport serving the Toluca and greater Mexico City area in Mexico.
  • D. MTT
    MTT is the acronym for Cuba’s Territorial Troops Militia, a large volunteer defense force integrated into the country’s national defense system.
  • E. TMO
    TMO is the stock ticker symbol for Thermo Fisher Scientific, a leading global provider of scientific instruments, reagents, and laboratory services.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8af18e4819091811bca657c9cb0 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e483ec6ca8819082713a278c987756 completed April 19, 2026, 7:27 a.m.
Created at: April 8, 2026, 9:29 p.m.