Triple

T16721273
Position Surface form Disambiguated ID Type / Status
Subject Ialyssos E406352 entity
Predicate hasNearbyAncientRemains P14422 FINISHED
Object Hellenistic and Roman ruins 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: Hellenistic and Roman ruins | Statement: [Ialyssos, hasNearbyAncientRemains, Hellenistic and Roman ruins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyAncientRemains
Context triple: [Ialyssos, hasNearbyAncientRemains, Hellenistic and Roman ruins]
  • A. hasNearbyArchaeologicalSite chosen
    Indicates that an entity is located close to or in the vicinity of an archaeological site.
  • B. hasNearbyAncientCity
    Indicates that one entity is located close to another entity that is classified as an ancient city.
  • C. hasArchaeologicalMound
    Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
  • D. hasArchaeologicalSiteIn
    Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
  • E. hasArchaeologicalFeature
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
  • F. None of above.

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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38743750c81908a980372ad8f1a6a completed April 18, 2026, 1:29 p.m.
PD Predicate disambiguation batch_69e319c379f88190ac0adf812486f598 completed April 18, 2026, 5:42 a.m.
Created at: April 10, 2026, 5:20 a.m.