Triple
T16095343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVC |
E390466
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Traverse City |
—
|
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: Traverse City | Statement: [TVC, nearCity, Traverse City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Traverse City Context triple: [TVC, nearCity, Traverse City]
-
A.
Traverse City, Michigan
chosen
Traverse City, Michigan is a popular northern Michigan destination known for its cherry production, vibrant downtown, and outdoor recreation along the shores of Grand Traverse Bay.
-
B.
Saginaw
Saginaw is a city in central Michigan known for its industrial history, location along the Saginaw River, and role as a regional economic and cultural center.
-
C.
Saginaw
Saginaw is a residential suburb located within the greater Dallas urban area.
-
D.
Harbor Springs
Harbor Springs is a small resort town on the shores of Lake Michigan known for its scenic harbor, historic charm, and year-round outdoor recreation.
-
E.
Augusta, Michigan
Augusta, Michigan is a small village in southwestern Michigan known for its rural character and proximity to the city of Kalamazoo.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1859283008190baac96142b5c7e53 |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:59 a.m.