Triple

T5037787
Position Surface form Disambiguated ID Type / Status
Subject Sokar E113468 entity
Predicate hasAlternativeName P39 FINISHED
Object Sokaris E161828 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: Sokaris | Statement: [Sokar, hasAlternativeName, Sokaris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sokaris
Context triple: [Sokar, hasAlternativeName, Sokaris]
  • A. Navigo
    Navigo is the contactless smart card ticketing system used for public transportation across the Île-de-France region, including Paris.
  • B. Sokar chosen
    Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
  • C. Arsacia
    Arsacia is an alternative name historically used for the city of Rayy (near modern-day Tehran) in ancient Persia.
  • D. Miaoulis
    Miaoulis is a Greek surname most famously associated with Admiral Andreas Miaoulis, a key naval leader in the Greek War of Independence.
  • E. Soter
    Soter is a Greek term meaning "savior" or "deliverer," often used as a title for deities or revered figures who provide salvation or protection.
  • 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_69bd44384298819089c49e7c330ec7b8 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73daaa788190b670f6c328bfa44f completed March 20, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9c7c8ba881908240c7f338ad9784 completed March 21, 2026, 1:26 p.m.
Created at: March 20, 2026, 1:37 p.m.