Triple

T11749999
Position Surface form Disambiguated ID Type / Status
Subject EFIK E279379 entity
Predicate servesCity P82 FINISHED
Object Jyväskylä E77953 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: Jyväskylä | Statement: [EFIK, servesCity, Jyväskylä]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jyväskylä
Context triple: [EFIK, servesCity, Jyväskylä]
  • A. Jyväskylä chosen
    Jyväskylä is a central Finnish city known for its lakeside setting, strong educational institutions, and association with architect Alvar Aalto.
  • B. Joensuu
    Joensuu is a city in eastern Finland that serves as a regional center for North Karelia, known for its university, forestry industry, and proximity to lakes and forests.
  • C. Lahti
    Lahti is a city in southern Finland known for its winter sports facilities, particularly ski jumping and cross-country skiing, and for hosting numerous international sporting events.
  • D. Kouvola
    Kouvola is a city in southeastern Finland known as a regional transport hub and gateway to the nearby Repovesi National Park.
  • E. Kuopio
    Kuopio is a city in eastern Finland known for its lakeside setting, vibrant cultural life, and status as a regional center for education and commerce.
  • 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_69d6ab01038c819080714901502c84fc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a508b0c4819082fbcc27d559ea2f completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd466577508190b1926c475b7c49dc completed May 8, 2026, 2:11 a.m.
Created at: April 8, 2026, 9:41 p.m.