Triple

T3543190
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Granicus E74933 entity
Predicate AlexanderRisk P48781 FINISHED
Object Alexander nearly killed in combat 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: Alexander nearly killed in combat | Statement: [Battle of the Granicus, AlexanderRisk, Alexander nearly killed in combat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AlexanderRisk
Context triple: [Battle of the Granicus, AlexanderRisk, Alexander nearly killed in combat]
  • A. riskModel
    Indicates a relationship where an entity serves as or is associated with a model used to assess, quantify, or manage risk for another entity or situation.
  • B. riskBasis
    Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
  • C. riskType
    Indicates the category or nature of risk associated with an entity, event, or relationship.
  • D. riskAllocation
    Indicates how the potential negative consequences or uncertainties of an action, event, or agreement are distributed among the involved parties.
  • E. riskManagement
    Indicates the implementation of strategies and actions to identify, assess, and mitigate potential risks associated with an entity or activity.
  • F. None of above. chosen

Provenance (4 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_69ad85d274cc8190ab59c97298a1cfbf completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbf752dd481909226044ffe595338 completed March 8, 2026, 6:27 p.m.
PD Predicate disambiguation batch_69adae15749881909b847c6ca73c934e completed March 8, 2026, 5:12 p.m.
PDg Predicate description generation batch_69adb0a11a1c8190baa8c0eb87ad259a completed March 8, 2026, 5:23 p.m.
Created at: March 8, 2026, 3:20 p.m.