Triple

T18867322
Position Surface form Disambiguated ID Type / Status
Subject Anput E461472 entity
Predicate worshipPlace P1191 FINISHED
Object Lycopolis NE NERFINISHED

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: Lycopolis | Statement: [Anput, worshipPlace, Lycopolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lycopolis
Context triple: [Anput, worshipPlace, Lycopolis]
  • A. Lycopolis chosen
    Lycopolis was an ancient Egyptian city, located in Upper Egypt, known as the birthplace of the Neoplatonist philosopher Plotinus.
  • B. Leontopolis
    Leontopolis was an ancient Egyptian city in the Nile Delta notable for its temple complex and cult dedicated to lion-associated deities.
  • C. Ptolemais
    Ptolemais is an ancient Greek and later Roman city on the coast of modern Libya, notable for its well-preserved ruins and role as a major urban center in the Cyrenaica region.
  • D. Ptolemais
    Ptolemais is the historical name of the ancient Mediterranean port city now known as Acre in modern-day Israel.
  • E. Karanis
    Karanis is an ancient Greco-Roman agricultural town in Egypt’s Faiyum region, known for its well-preserved houses, papyri, and temples that illuminate daily life in Roman Egypt.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c2a617548190be6044bf2c3de6d0 completed April 20, 2026, 6:07 a.m.
Created at: April 10, 2026, 11:57 a.m.