Triple

T30198422
Position Surface form Disambiguated ID Type / Status
Subject Lords of Thasos E767697 entity
Predicate hasFeudalControlOver P48704 FINISHED
Object Thasos NE NERFINISHED

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: Thasos | Statement: [Lords of Thasos, hasFeudalControlOver, Thasos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeudalControlOver
Context triple: [Lords of Thasos, hasFeudalControlOver, Thasos]
  • A. hasFeudalOverlord
    Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
  • B. isFeudalState
    Indicates that a political entity operates under a feudal system, where power is decentralized and structured through hierarchical obligations between lords and vassals.
  • C. isFeudal
    Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
  • D. feudalCenter
    Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
  • E. feudalJurisdictionOver chosen
    Indicates that one entity holds legal and administrative authority or control over another entity within a feudal system.
  • 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_69f2247db1108190835c0727c97637c3 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f71996e1a48190ac59a1d66d7c44e8 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71820c6c88190ab38b4fa626d22cc completed May 3, 2026, 9:40 a.m.
Created at: April 29, 2026, 7:30 p.m.