Triple

T19222990
Position Surface form Disambiguated ID Type / Status
Subject Jon Gruden E480665 entity
Predicate familyName P18 FINISHED
Object Gruden 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: Gruden | Statement: [Jon Gruden, familyName, Gruden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gruden
Context triple: [Jon Gruden, familyName, Gruden]
  • A. Gruden chosen
    Gruden is a surname most prominently associated with Jon Gruden, a former NFL head coach and television analyst.
  • B. Grunnegs
    Grunnegs is the local endonym for the Gronings dialect of Low Saxon spoken in the Dutch province of Groningen and surrounding areas.
  • C. Grødem
    Grødem is a coastal village in Randaberg municipality in Rogaland county, Norway, known for its residential areas and proximity to the city of Stavanger.
  • D. Gransherad
    Gransherad was a former rural municipality in Telemark county, Norway, known for its agricultural landscape and later incorporation into the municipality of Notodden.
  • E. Grossgrunden
    Grossgrunden is one of the islands in the Holmön archipelago off the coast of northern Sweden in the Gulf of Bothnia.
  • 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_69d8e8ccb8f48190ad420098e74fb1db completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fa94aed081909045cfed8edc6039 completed April 20, 2026, 10:06 a.m.
Created at: April 10, 2026, 1:24 p.m.