Triple

T17306612
Position Surface form Disambiguated ID Type / Status
Subject Vladimir Makarov E420179 entity
Predicate goalInFiction P42284 FINISHED
Object destabilize global order 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: destabilize global order | Statement: [Vladimir Makarov, goalInFiction, destabilize global order]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: goalInFiction
Context triple: [Vladimir Makarov, goalInFiction, destabilize global order]
  • A. targetInFiction
    Indicates that one entity is the target or subject of an action, focus, or effect within a fictional work or narrative context.
  • B. hasFictionalGoal
    Indicates that an entity is associated with a goal or objective that exists only within a fictional, imagined, or narrative context.
  • C. designedPurposeInFiction
    Indicates that something is intentionally created within a fictional context to serve a particular role, function, or narrative purpose.
  • D. goalIn
    Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
  • E. narrativeGoal chosen
    Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e438ff3ee08190ab4c44a22f86b38b completed April 19, 2026, 2:07 a.m.
PD Predicate disambiguation batch_69e3b01b9d1c8190a406dd941c9b11a1 completed April 18, 2026, 4:23 p.m.
Created at: April 10, 2026, 5:43 a.m.