Triple

T18866192
Position Surface form Disambiguated ID Type / Status
Subject Niš Fortress E461442 entity
Predicate functionDuringOttomanPeriod P133247 FINISHED
Object military stronghold 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: military stronghold | Statement: [Niš Fortress, functionDuringOttomanPeriod, military stronghold]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: functionDuringOttomanPeriod
Context triple: [Niš Fortress, functionDuringOttomanPeriod, military stronghold]
  • A. underOttomanRuleFrom
    Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
  • B. functionDuringImperialEra
    Indicates that a function, role, or activity occurred or was in effect during the imperial era.
  • C. notUnderFullOttomanControl
    Indicates that the entity or region was not completely governed, administered, or dominated by the Ottoman Empire.
  • D. functionDuringMonarchy
    Indicates that the function, role, or activity occurs or is in effect during a period of monarchy.
  • E. countryDuringOttomanUse
    Indicates that a specified country existed or held authority over a place or entity during the period of Ottoman rule or influence.
  • F. None of above. chosen

Provenance (4 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_69e5c2a5074481908941fcbb3b3eefa2 completed April 20, 2026, 6:07 a.m.
PD Predicate disambiguation batch_69e48d2166b88190add38de96cedc65c completed April 19, 2026, 8:06 a.m.
PDg Predicate description generation batch_69e49785fd7081909577e90a55df0a35 completed April 19, 2026, 8:51 a.m.
Created at: April 10, 2026, 11:57 a.m.