Triple

T27770747
Position Surface form Disambiguated ID Type / Status
Subject United by Football – Vereint im Herzen Europas E701736 entity
Predicate germanPart P163236 FINISHED
Object Vereint im Herzen Europas 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: Vereint im Herzen Europas | Statement: [United by Football – Vereint im Herzen Europas, germanPart, Vereint im Herzen Europas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: germanPart
Context triple: [United by Football – Vereint im Herzen Europas, germanPart, Vereint im Herzen Europas]
  • A. locatedInPartOfGermany
    Indicates that one entity is geographically situated within a specific region or part of Germany.
  • B. germanUnit
    Indicates that an entity is a military or organizational unit that belongs to, originates from, or is associated with Germany.
  • C. containsGermanSpeakingArea
    Indicates that one entity geographically includes an area where German is predominantly spoken.
  • D. oneOfGermanys
    Indicates that something or someone belongs to the set of entities that are part of, originate from, or are associated with Germany.
  • E. objectiveGermany
    Indicates that an entity has Germany as its objective, target, or goal in a given context.
  • 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_69ef6a52fa708190934a32308d2c92dc completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f637962be88190b63239f6e4b782f4 completed May 2, 2026, 5:42 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 4:34 p.m.