Triple

T10443288
Position Surface form Disambiguated ID Type / Status
Subject Warsaw Modlin Airport E246220 entity
Predicate nearbyTown P3883 FINISHED
Object Modlin E246221 NE 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: Modlin | Statement: [Warsaw Modlin Airport, nearbyTown, Modlin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Modlin
Context triple: [Warsaw Modlin Airport, nearbyTown, Modlin]
  • A. Modlin chosen
    Modlin is a village in Poland best known for its historic fortress and for giving its name to Warsaw Modlin Airport, a secondary airport serving the Warsaw area.
  • B. Mogilno
    Mogilno is a historic town in north-central Poland known for its medieval monastery and location in the Kuyavian-Pomeranian Voivodeship.
  • C. Modri
    Modri is the popular nickname of Croatian football club GNK Dinamo Zagreb, reflecting the team’s traditional blue colors.
  • D. Modrow
    Modrow is a German surname most notably associated with Hans Modrow, the last communist premier of East Germany.
  • E. Flerzheim
    Flerzheim is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d381c04fe08190957c26c526a3b05a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4fdbd731c819084dfff83b4481ae8 completed April 7, 2026, 12:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69d89fa5b3b081909af7de1745372add completed April 10, 2026, 6:58 a.m.
Created at: April 6, 2026, 12:15 p.m.