Triple
T14790239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Michigan |
E347633
|
entity |
| Predicate | majorCity |
P316
|
FINISHED |
| Object | Lansing |
E16556
|
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: Lansing | Statement: [Southern Michigan, majorCity, Lansing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lansing Context triple: [Southern Michigan, majorCity, Lansing]
-
A.
Lansing
Lansing is a surname of English origin borne by various notable individuals, including American statesman Robert Lansing.
-
B.
Lansing
Lansing is a small village located within Tompkins County in central New York State, near the city of Ithaca.
-
C.
Lansing, Michigan
chosen
Lansing, Michigan is the capital city of the U.S. state of Michigan and a historic center of automobile manufacturing and industry.
-
D.
Kalamazoo
Kalamazoo is a mid-sized city in southwestern Michigan known for its historic downtown, educational institutions like Western Michigan University, and a legacy of manufacturing and craft beer.
-
E.
Saginaw
Saginaw is a residential suburb located within the greater Dallas urban area.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe388fc0e08190a758a1e0a4140909 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:31 a.m.