Triple

T22437339
Position Surface form Disambiguated ID Type / Status
Subject Riksdrots E554659 entity
Predicate seeAlso P37 FINISHED
Object Riksmarsk NE NERFINISHED

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: Riksmarsk | Statement: [Riksdrots, seeAlso, Riksmarsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riksmarsk
Context triple: [Riksdrots, seeAlso, Riksmarsk]
  • A. Riksmarsk chosen
    Riksmarsk was the historical title for Sweden’s highest military commander and one of the great officers of the realm.
  • B. Riasti
    Riasti is a regional dialect of the Saraiki language spoken primarily in parts of southern Punjab, Pakistan.
  • C. Rylsk
    Rylsk is a historic town that once served as the political and administrative center of the medieval Principality of Rylsk in Eastern Europe.
  • D. Stadhavet
    Stadhavet is a notoriously rough stretch of open sea off the western coast of Norway, known for its challenging weather and hazardous sailing conditions.
  • E. Tõdva-Riisu
    Tõdva-Riisu is a small village located in Saku Parish in northern Estonia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15adf52f08190a5b592be3e68af0f completed April 29, 2026, 1:11 a.m.
Created at: April 16, 2026, 8:47 p.m.