Triple

T25223028
Position Surface form Disambiguated ID Type / Status
Subject De Indis E632012 entity
Predicate positionOnConquest P22409 FINISHED
Object questions automatic legitimacy of conquest 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: questions automatic legitimacy of conquest | Statement: [De Indis, positionOnConquest, questions automatic legitimacy of conquest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionOnConquest
Context triple: [De Indis, positionOnConquest, questions automatic legitimacy of conquest]
  • A. afterConquest
    Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
  • B. roleDuringConquest chosen
    Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
  • C. conqueredIn
    Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
  • D. attemptedConquest
    Indicates that one entity tried, but did not necessarily succeed, to conquer, subjugate, or take control of another entity.
  • E. afterConquestBy
    Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
  • 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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6456608190b94e7c2e2c2a4824 completed May 2, 2026, 6:03 p.m.
Created at: April 21, 2026, 1:03 p.m.