Triple

T104937
Position Surface form Disambiguated ID Type / Status
Subject Mercury (branch) insignia E2118 entity
Predicate representsDeity P5782 FINISHED
Object Roman god of messages and commerce LITERAL 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: Roman god of messages and commerce | Statement: [Mercury (branch) insignia, representsDeity, Roman god of messages and commerce]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: representsDeity
Context triple: [Mercury (branch) insignia, representsDeity, Roman god of messages and commerce]
  • A. worshipsDeity
    Indicates that one entity reveres, honors, or performs religious devotion toward another entity regarded as a deity.
  • B. worshippedIn
    Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
  • C. roleInTheology
    Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
  • D. hasRitual
    Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
  • E. representsCity
    Indicates that one entity serves as the official representative or embodiment of a particular city.
  • F. None of above. chosen

Provenance (4 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_69a24e0a5b7c81908d52da08c60dabc4 completed Feb. 28, 2026, 2:08 a.m.
NER Named-entity recognition batch_69a25711f6788190a22252ea3a3af394 completed Feb. 28, 2026, 2:46 a.m.
PD Predicate disambiguation batch_69a2563be81c81908ccc5ed44edd6b8e completed Feb. 28, 2026, 2:43 a.m.
PDg Predicate description generation batch_69a2570f45bc81909ebba7ee5f602976 completed Feb. 28, 2026, 2:46 a.m.
Created at: Feb. 28, 2026, 2:12 a.m.