Triple

T2457345
Position Surface form Disambiguated ID Type / Status
Subject Vulcano E54452 entity
Predicate namedAfter P63 FINISHED
Object Vulcan E15463 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: Vulcan | Statement: [Vulcano, namedAfter, Vulcan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vulcan
Context triple: [Vulcano, namedAfter, Vulcan]
  • A. Vulcan chosen
    Vulcan is the Roman god of fire, metalworking, and the forge, often depicted as a blacksmith crafting weapons and armor for the gods.
  • B. Vulcano
    Vulcano is a small volcanic island in Italy’s Aeolian archipelago, famed for its active fumaroles, hot springs, and historical role in giving volcanoes their name.
  • C. Venera
    Venera is a grade or class within the Mexican Order of the Aztec Eagle, the country’s highest distinction awarded to foreigners.
  • D. Mondas
    Mondas is the fictional twin planet of Earth in the Doctor Who universe, known as the original home of the Cybermen.
  • E. Varuna
    Varuna is an ancient Vedic god primarily associated with cosmic order, moral law, and the waters, often regarded as a sovereign guardian of ṛta (universal order).
  • 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_69ab49dee84c819096b50a0049c347ac completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd10860188190bfc4c554914487b4 completed March 7, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69aef0ca655c81908612983ced5f5786 completed March 9, 2026, 4:09 p.m.
Created at: March 6, 2026, 9:44 p.m.