Triple

T14698693
Position Surface form Disambiguated ID Type / Status
Subject Iberica (Spanish Wars) E345230 entity
Predicate describesConflictType P1397 FINISHED
Object Roman wars 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: Roman wars of conquest | Statement: [Iberica (Spanish Wars), describesConflictType, Roman wars of conquest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: describesConflictType
Context triple: [Iberica (Spanish Wars), describesConflictType, Roman wars of conquest]
  • A. conflictType chosen
    Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
  • B. conflictDescribedIn
    Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
  • C. usedInConflictType
    Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
  • D. featuresConflictType
    Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
  • E. reportedConflict
    Indicates that one party has formally reported the existence of a conflict involving another party or situation.
  • 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_69d822e4a8c08190a155df736bb7bc13 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb604f88081908a677175045496d0 completed April 14, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69de657c57ec8190ae0b9bb79a514566 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:28 a.m.