Triple

T8345706
Position Surface form Disambiguated ID Type / Status
Subject Antigonus I Monophthalmus E196027 entity
Predicate ambition P24003 FINISHED
Object to reunite Alexander’s empire under his rule 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: to reunite Alexander’s empire under his rule | Statement: [Antigonus I Monophthalmus, ambition, to reunite Alexander’s empire under his rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ambition
Context triple: [Antigonus I Monophthalmus, ambition, to reunite Alexander’s empire under his rule]
  • A. aimOf
    Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
  • B. goals
    Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
  • C. commitment
    Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
  • D. territorialAmbition chosen
    Indicates a desire or intent by one entity to expand its control, ownership, or influence over additional geographic areas or territories.
  • E. aspect
    Indicates a specific temporal phase or manner in which an action, event, or state unfolds or is viewed (e.g., ongoing, completed, habitual).
  • 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_69ca82edd63c8190b876b8465464c5fa completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7feef7e8819084ca0441d146bac7 completed March 31, 2026, 8:03 a.m.
PD Predicate disambiguation batch_69cb70c6d0ec8190acf273b0e007b51a completed March 31, 2026, 6:59 a.m.
Created at: March 30, 2026, 5:58 p.m.