Triple

T33920708
Position Surface form Disambiguated ID Type / Status
Subject Yakapınar E869598 entity
Predicate hasNearbyFortifications P66389 FINISHED
Object medieval fortifications of Mopsuestia 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: medieval fortifications of Mopsuestia | Statement: [Yakapınar, hasNearbyFortifications, medieval fortifications of Mopsuestia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyFortifications
Context triple: [Yakapınar, hasNearbyFortifications, medieval fortifications of Mopsuestia]
  • A. hasFortificationNearby chosen
    Indicates that one entity is located in proximity to, or within the immediate area of, a fortification structure associated with it.
  • B. hasFortificationsFrom
    Indicates that an entity possesses or is protected by fortifications that originate from or were constructed by another specified source or period.
  • C. hasFortifications
    Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
  • D. hasNearbyMilitaryTown
    Indicates that one location is situated close to a town whose primary function or identity is associated with military presence or activity.
  • E. hasFortificationTarget
    Indicates that a fortification action is directed toward or applied to a specific target entity.
  • 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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff9b1ad27081908f8a492396950795 completed May 9, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69ff9a6354c48190ae21070c1424cb7a completed May 9, 2026, 8:34 p.m.
Created at: May 1, 2026, 1:49 a.m.