Triple

T5760462
Position Surface form Disambiguated ID Type / Status
Subject Comes de Fyf E127077 entity
Predicate hasFeudalContext P18765 FINISHED
Object Scottish feudal system 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: Scottish feudal system | Statement: [Comes de Fyf, hasFeudalContext, Scottish feudal system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeudalContext
Context triple: [Comes de Fyf, hasFeudalContext, Scottish feudal system]
  • A. isFeudal
    Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
  • B. hasFeudalOverlord
    Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
  • C. associatedWithFeudalSystem chosen
    Indicates a relationship in which something is connected, linked, or relevant to the structures, practices, or institutions of a feudal system.
  • D. laterFeudalStatus
    Indicates that one entity held a particular feudal status or rank at a later time than another entity or than an earlier status.
  • E. feudalType
    Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
  • 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_69c00833a3fc81908f4bc29ed011b7a6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02938972c8190992149ea943f87bf completed March 22, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69c021cc68648190bb86d049ebe80f12 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:49 p.m.