Triple

T2690675
Position Surface form Disambiguated ID Type / Status
Subject Ypsilanti E58392 entity
Predicate hasNickname P39 FINISHED
Object Ypsi E58392 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: Ypsi | Statement: [Ypsilanti, hasNickname, Ypsi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ypsi
Context triple: [Ypsilanti, hasNickname, Ypsi]
  • A. Ypsilanti chosen
    Ypsilanti is a city in southeastern Michigan known for Eastern Michigan University and its historic downtown and automotive heritage.
  • B. Grosse Pointe Park
    Grosse Pointe Park is a suburban city bordering Detroit in southeastern Michigan, known for its affluent residential character and location along Lake St. Clair.
  • C. Ferndale
    Ferndale is a former coal-mining town and community located in the Rhondda Fach valley in south Wales.
  • D. Grosse Pointe, Michigan
    Grosse Pointe, Michigan is an affluent suburban city bordering Detroit, known for its historic lakeside homes, tree-lined streets, and upscale residential character.
  • E. Oakland Hills
    Oakland Hills is a predominantly residential, hilly region in Oakland, California, known for its scenic views, winding roads, and affluent neighborhoods nestled in the East Bay hills.
  • 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_69ab4ac269e481909cb317d79e68b75b completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda0ba2208190ad87763ecbef8c3c completed March 7, 2026, 7:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69afaf61b83c8190ab254d927cb908f2 completed March 10, 2026, 5:42 a.m.
Created at: March 6, 2026, 9:54 p.m.