Triple

T8873680
Position Surface form Disambiguated ID Type / Status
Subject Michigan State University E211215 entity
Predicate locatedIn P40 FINISHED
Object East Lansing E52734 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: East Lansing | Statement: [Michigan State University, locatedIn, East Lansing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: East Lansing
Context triple: [Michigan State University, locatedIn, East Lansing]
  • A. East Lansing chosen
    East Lansing is a city in central Michigan best known as the home of Michigan State University.
  • B. Ann Arbor
    Ann Arbor is a vibrant college town in southeastern Michigan best known as the home of the University of Michigan and a center for education, research, and arts.
  • C. Lansing, Michigan
    Lansing, Michigan is the capital city of the U.S. state of Michigan and a historic center of automobile manufacturing and industry.
  • D. Lansing
    Lansing is a surname of English origin borne by various notable individuals, including American statesman Robert Lansing.
  • E. Lansing
    Lansing is a small village located within Tompkins County in central New York State, near the city of Ithaca.
  • 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_69ca838e78748190934d82db3104f855 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc614451d081908804430a72d00edf completed April 1, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69d152541308819098cdca4f3ba9011d completed April 4, 2026, 6:03 p.m.
Created at: March 30, 2026, 6:52 p.m.