Triple

T7161085
Position Surface form Disambiguated ID Type / Status
Subject York, England E166944 entity
Predicate VikingName P28503 FINISHED
Object Jorvik E171529 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: Jorvik | Statement: [York, England, VikingName, Jorvik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jorvik
Context triple: [York, England, VikingName, Jorvik]
  • A. Jórvík chosen
    Jórvík is the Old Norse name for the city of York during its period as a major Viking settlement and trading center in early medieval England.
  • B. City of York
    The City of York is a historic cathedral city in North Yorkshire, England, renowned for its medieval walls, Gothic York Minster, and well-preserved old town.
  • C. Ripon
    Ripon is a small city in California’s Central Valley known for its agricultural roots and tight-knit community.
  • D. Ripon
    Ripon is a historic cathedral city in North Yorkshire, England, known for Ripon Cathedral and its traditional hornblower ceremony.
  • E. Lundenwic
    Lundenwic was the early medieval trading settlement and urban center of the Middle Saxons that preceded the later walled city of London.
  • 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_69c68887a5cc8190bec0ea96227164f7 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e82ce770819081dccf7ffd50c2ab completed March 27, 2026, 8:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7adc08b688190a00024727542c8b9 completed March 28, 2026, 10:30 a.m.
Created at: March 27, 2026, 2:47 p.m.