Triple

T3851651
Position Surface form Disambiguated ID Type / Status
Subject early Ottoman period E85306 entity
Predicate hasMilitaryInstitution P4889 FINISHED
Object early Janissary corps 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: early Janissary corps | Statement: [early Ottoman period, hasMilitaryInstitution, early Janissary corps]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMilitaryInstitution
Context triple: [early Ottoman period, hasMilitaryInstitution, early Janissary corps]
  • A. institutionOfDefense
    Indicates that an entity functions as an organization responsible for defense or military protection within a given jurisdiction or context.
  • B. introducedMilitaryInstitution
    Indicates that an entity established or brought into existence a military institution or organization.
  • C. hasMilitaryBase
    Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
  • D. hasMilitaryPresence
    Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
  • E. militaryOrganization chosen
    Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
  • 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_69aed936de1c81908f91bed80f70abb2 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeebd0feb081909cc1d5bf41e4acd6 completed March 9, 2026, 3:48 p.m.
PD Predicate disambiguation batch_69aee750377c8190af70c79768c0edd8 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:19 p.m.