Triple

T17594946
Position Surface form Disambiguated ID Type / Status
Subject Sopron plebiscite of 1921 E428544 entity
Predicate resultForAustria P128146 FINISHED
Object loss of claim to Sopron city 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: loss of claim to Sopron city | Statement: [Sopron plebiscite of 1921, resultForAustria, loss of claim to Sopron city]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resultForAustria
Context triple: [Sopron plebiscite of 1921, resultForAustria, loss of claim to Sopron city]
  • A. AustrianObjective
    Indicates that an entity has an objective, goal, or purpose specifically associated with Austria or Austrian context.
  • B. AustrianStrength
    Indicates a relationship where an entity possesses or exhibits strength specifically associated with Austria, such as Austrian power, influence, or capability.
  • C. resultInHungary
    Indicates that an action, event, or process leads to an outcome that occurs in or pertains specifically to Hungary.
  • D. AustrianCasualtiesApprox
    Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
  • E. chartPositionAustria
    Indicates the position or ranking that something holds on a music or sales chart specifically in Austria.
  • 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e469ead59c8190a06519311891af3c completed April 19, 2026, 5:36 a.m.
PD Predicate disambiguation batch_69e3b4fff0348190b899a32da537eaca completed April 18, 2026, 4:44 p.m.
PDg Predicate description generation batch_69e3bbb50b448190a59dd4be33c76db7 completed April 18, 2026, 5:13 p.m.
Created at: April 10, 2026, 5:51 a.m.