Triple

T15345196
Position Surface form Disambiguated ID Type / Status
Subject European route E39 E366897 entity
Predicate connects P390 FINISHED
Object Vestland E75761 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: Vestland | Statement: [European route E39, connects, Vestland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vestland
Context triple: [European route E39, connects, Vestland]
  • A. Vestland chosen
    Vestland is a county in western Norway known for its dramatic fjords, coastal landscapes, and the city of Bergen.
  • B. Vestlandet
    Vestlandet is the western region of Norway, known for its dramatic fjords, mountains, and coastal landscapes.
  • C. Skåneland
    Skåneland is a historical region in southern Scandinavia encompassing the provinces around present-day Skåne, known for its shifting rule between Denmark and Sweden and its central role in medieval Nordic history.
  • D. Albvorland
    Albvorland is a scenic foreland region at the foot of the Swabian Jura in southern Germany, characterized by rolling landscapes and views toward the Alb plateau.
  • E. Fosen
    Fosen is a peninsula and traditional district in central Norway known for its coastal landscape, wind farms, and location across the Trondheimsfjord from the city of Trondheim.
  • 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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e163a3c8190ab933411372c1573 completed April 16, 2026, 1:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff56b4c6c881908ac7887a88f80829 completed May 9, 2026, 3:45 p.m.
Created at: April 10, 2026, 3:17 a.m.