Triple

T3543189
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Granicus E74933 entity
Predicate AlexanderRole P11687 FINISHED
Object personally led the Companion cavalry charge 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: personally led the Companion cavalry charge | Statement: [Battle of the Granicus, AlexanderRole, personally led the Companion cavalry charge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AlexanderRole
Context triple: [Battle of the Granicus, AlexanderRole, personally led the Companion cavalry charge]
  • A. deFactoRole
    Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
  • B. systemRole
    Indicates the functional position or responsibility that an entity holds within a larger system or structure.
  • C. unitRole
    Indicates the functional role or purpose that a unit serves within a larger system or context.
  • D. servesRole chosen
    Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
  • E. roleInTheology
    Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
  • 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_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.
Created at: March 8, 2026, 3:20 p.m.