Triple

T17284570
Position Surface form Disambiguated ID Type / Status
Subject Toribio E419617 entity
Predicate hasLatinForm P3646 FINISHED
Object Turibius E1261848 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: Turibius | Statement: [Toribio, hasLatinForm, Turibius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Turibius
Context triple: [Toribio, hasLatinForm, Turibius]
  • A. Turibius chosen
    Turibius is a masculine given name, historically associated with several Christian saints and used as a variant of the name Toribio.
  • B. Ubalde
    Ubalde is a character in the opera "Armide," typically portrayed as a valiant knight who attempts to rescue the enchanted Renaud.
  • C. Thurinus
    Thurinus was an early cognomen of the Roman statesman Gaius Octavius, who later became the first Roman emperor Augustus.
  • D. Famedio
    Famedio is a grand memorial chapel and pantheon within Milan’s Monumental Cemetery, dedicated to honoring the city’s most illustrious citizens.
  • E. Dionisio
    Dionisio is a masculine given name of Greek origin, derived from Dionysius and associated with the ancient Greek god Dionysus.
  • 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_69d886da626481908a14ce7830329a35 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e4332bd324819080795152293d6d43 completed April 19, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a018c407fe8819095b16b171f29cf1b completed May 11, 2026, 7:58 a.m.
Created at: April 10, 2026, 5:40 a.m.