Triple

T22660776
Position Surface form Disambiguated ID Type / Status
Subject Tolo E559654 entity
Predicate near P350 FINISHED
Object Tiryns 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: Tiryns | Statement: [Tolo, near, Tiryns]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tiryns
Context triple: [Tolo, near, Tiryns]
  • A. Tiryns chosen
    Tiryns is an important archaeological site in the northeastern Peloponnese of Greece, known for its Mycenaean citadel and massive Cyclopean walls.
  • B. Nea Tiryntha
    Nea Tiryntha is a modern Greek village near the archaeological site of ancient Tiryns in the Argolis region of the Peloponnese.
  • C. Mycenae
    Mycenae was a major ancient Greek city and powerful Bronze Age citadel in the northeastern Peloponnese, famed as the legendary seat of King Agamemnon and a center of Mycenaean civilization.
  • D. Pylos
    Pylos is an ancient town in Messenia, Greece, known from Homeric epics and later Greek tradition as a significant Mycenaean center and legendary seat of King Nestor.
  • E. Argēs
    Argēs is a figure from Greek mythology, traditionally known as one of the Cyclopes associated with thunder and lightning.
  • 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_69e2454a158c819093b8e35f5045efb6 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1765edf88819086c28525e3c73758 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 3:07 p.m.