Triple

T14153318
Position Surface form Disambiguated ID Type / Status
Subject Grand Master E350742 entity
Predicate historicallyFoundIn P91166 FINISHED
Object medieval Europe 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 Europe | Statement: [Grand Master, historicallyFoundIn, medieval Europe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyFoundIn
Context triple: [Grand Master, historicallyFoundIn, medieval Europe]
  • A. historicallyObservedIn chosen
    Indicates that something has been recorded or documented as occurring, existing, or taking place within a particular historical context, period, or location.
  • B. historicallyBasedIn
    Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
  • C. historicallyPartOf
    Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
  • D. historicallyNativeTo
    Indicates that an entity has been originally or traditionally present in, or originating from, a particular place or region over a significant period in history.
  • E. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • 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_69d8278775fc8190b0802d22ca2f495d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6133754881908e1e97db71772deb completed April 14, 2026, 3:45 p.m.
PD Predicate disambiguation batch_69de05b8434c81908c33b1b513463b12 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 12:57 a.m.