Triple

T21807430
Position Surface form Disambiguated ID Type / Status
Subject kryzys gdański E538383 entity
Predicate związanyZ P2830 FINISHED
Object polsko-niemieckie stosunki dyplomatyczne 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: polsko-niemieckie stosunki dyplomatyczne | Statement: [kryzys gdański, związanyZ, polsko-niemieckie stosunki dyplomatyczne]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: związanyZ
Context triple: [kryzys gdański, związanyZ, polsko-niemieckie stosunki dyplomatyczne]
  • A. isAssociatedWith chosen
    Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
  • B. bondedWith
    Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
  • C. positionAssociatedWith
    Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
  • D. associatedVow
    Indicates a relationship where a vow is linked or connected to a particular entity or event.
  • E. notablyAssociatedWith
    Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
  • 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07803b4888190af06bf7a90198f60 completed April 28, 2026, 9:04 a.m.
PD Predicate disambiguation batch_69e6be751ce881909badced245ef76c7 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:53 p.m.