Triple

T4014307
Position Surface form Disambiguated ID Type / Status
Subject Earl of Lincoln E90717 entity
Predicate hasFeudalOrigin P1614 FINISHED
Object medieval England 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 England | Statement: [Earl of Lincoln, hasFeudalOrigin, medieval England]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeudalOrigin
Context triple: [Earl of Lincoln, hasFeudalOrigin, medieval England]
  • A. isFeudal
    Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
  • B. associatedWithFeudalSystem
    Indicates a relationship in which something is connected, linked, or relevant to the structures, practices, or institutions of a feudal system.
  • C. laterFeudalStatus
    Indicates that one entity held a particular feudal status or rank at a later time than another entity or than an earlier status.
  • D. hasHistoricalOrigin chosen
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • E. feudalStatus
    Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
  • 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_69aed95e44088190aff7d90a151b1b20 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaec08dc8190a341809059554f84 completed March 9, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69aef8fa6fec81909b1190ecbba61410 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:35 p.m.