Triple

T20824821
Position Surface form Disambiguated ID Type / Status
Subject Gairsay E512669 entity
Predicate hasHistoricalConnection P7843 FINISHED
Object Vikings 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: Vikings | Statement: [Gairsay, hasHistoricalConnection, Vikings]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vikings
Context triple: [Gairsay, hasHistoricalConnection, Vikings]
  • A. Vikings
    The Vikings are the athletic teams representing Portland State University in NCAA Division I sports.
  • B. Vikings chosen
    Vikings were seafaring Norse peoples from Scandinavia known for their raids, exploration, trade, and settlement across wide areas of Europe and the North Atlantic during the late eighth to early eleventh centuries.
  • C. Vikings
    The Vikings are the athletic teams representing Cleveland State University in NCAA Division I sports.
  • D. Vikings
    Vikings is a former team nickname once used by the University of Washington’s athletic programs before they became known as the Huskies.
  • E. Vikings
    The Vikings are the athletic teams representing Lawrence University in intercollegiate sports competitions.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2fcc60881908ef3d8914d801ea1 completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:41 p.m.