Triple

T16141735
Position Surface form Disambiguated ID Type / Status
Subject Plains (later period) E391672 entity
Predicate conflictDrivers P48690 FINISHED
Object competition for horses 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: competition for horses | Statement: [Plains (later period), conflictDrivers, competition for horses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conflictDrivers
Context triple: [Plains (later period), conflictDrivers, competition for horses]
  • A. triggersConflict
    Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
  • B. conflictWith
    Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
  • C. featuresConflictType
    Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
  • D. conflictUse
    Indicates a relationship where one entity’s use, application, or operation is incompatible with, obstructs, or negatively interferes with another entity’s use.
  • E. conflictSource chosen
    Indicates that one entity is the origin, cause, or initiating side of a conflict involving 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_69d87f1c65e48190aa2b4c472e9bafc4 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21a087c848190aba9ed2ccb422427 completed April 17, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69e182885bc08190822ae7e8a4b8ac1f completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 5:01 a.m.