Triple

T13442261
Position Surface form Disambiguated ID Type / Status
Subject Wisła Kraków E320392 entity
Predicate hasAbbreviation P43 FINISHED
Object WIS E320392 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: WIS | Statement: [Wisła Kraków, hasAbbreviation, WIS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WIS
Context triple: [Wisła Kraków, hasAbbreviation, WIS]
  • A. WIS
    WIS is the World Meteorological Organization’s global information system for sharing and distributing meteorological, hydrological, and related environmental data.
  • B. WIS
    WIS is the vehicle registration code used on license plates for the district of Nordwestmecklenburg in the German state of Mecklenburg-Vorpommern.
  • C. WIS chosen
    WIS is the common abbreviation for Wisła Kraków, a historic Polish football club based in Kraków.
  • D. W.D. Wis.
    W.D. Wis. is the standard legal abbreviation for the United States District Court for the Western District of Wisconsin, a federal trial court within the Seventh Circuit.
  • E. WIL
    WIL is the standard abbreviation used for the Wilmington Blue Rocks minor league baseball team.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee704ac8190b4c7f4e0d3a88494 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7399421908190a7750e37c89a73f6 completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:40 p.m.