Triple

T2359682
Position Surface form Disambiguated ID Type / Status
Subject Constantinus Magnus E47241 entity
Predicate ruledAs P10353 FINISHED
Object Roman emperor of the West 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: Roman emperor of the West | Statement: [Constantinus Magnus, ruledAs, Roman emperor of the West]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ruledAs
Context triple: [Constantinus Magnus, ruledAs, Roman emperor of the West]
  • A. alsoRuled
    Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
  • B. reignAs chosen
    Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
  • C. ruledFromRegion
    Indicates that a ruling authority exercised control or governance over a domain while being based in or operating from a specific region.
  • D. regentOf
    Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
  • E. periodOfRule
    Indicates the span of time during which an entity exercised authority, control, or governance over something.
  • 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_69a88a1a4a6081908645b0f2914521ab completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc720b9048190a5d3b19e5e1f373a completed March 7, 2026, 6:35 a.m.
PD Predicate disambiguation batch_69abc599b92c819093d9e15d4437705d completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:55 p.m.