Triple
T2813450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyandot |
E54226
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Huron |
E186544
|
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: Huron | Statement: [Wyandot, hasAlternativeName, Huron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huron Context triple: [Wyandot, hasAlternativeName, Huron]
-
A.
Huron
Huron is a small agricultural city located in California’s San Joaquin Valley.
-
B.
Huron
chosen
Huron is an Iroquoian language historically spoken by the Wyandot (Huron) people of the Great Lakes region in North America.
-
C.
St. Clair
St. Clair is a Scottish-origin surname historically associated with nobility and military and political figures in the English-speaking world.
-
D.
Nashwaaksis
Nashwaaksis is a residential neighbourhood in the city of Fredericton, New Brunswick, Canada.
-
E.
Nipissing
Nipissing is a former federal electoral district in Ontario, Canada, that historically represented communities in the Nipissing region before being redistributed into new ridings such as Renfrew—Nipissing—Pembroke.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4ba34c819085a336498fc326b0 |
completed | March 7, 2026, 8:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce9cd4ec81908900ffee0edb70ca |
completed | March 10, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:59 p.m.