Triple

T11208342
Position Surface form Disambiguated ID Type / Status
Subject Lucanians E265233 entity
Predicate lostAutonomy P76678 FINISHED
Object after Roman conquest in 3rd century BC 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: after Roman conquest in 3rd century BC | Statement: [Lucanians, lostAutonomy, after Roman conquest in 3rd century BC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lostAutonomy
Context triple: [Lucanians, lostAutonomy, after Roman conquest in 3rd century BC]
  • A. gainedAutonomy
    Indicates that an entity has transitioned from being controlled or dependent to having the ability to act or decide independently.
  • B. lostAuthorityOver
    Indicates that an entity no longer holds control, power, or decision-making authority over another entity or domain it previously governed.
  • C. lostSovereignty chosen
    Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
  • D. gainedAutonomyFrom
    Indicates that one entity obtained independence or self-governing control from another entity that previously held authority over it.
  • E. lost
    Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
  • 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_69d6aac59460819089b9848b27f57848 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d5f8908190903817f84c629ba1 completed April 9, 2026, 5:58 p.m.
PD Predicate disambiguation batch_69d75cf83464819087529d47d025d313 completed April 9, 2026, 8:02 a.m.
Created at: April 8, 2026, 9:30 p.m.