Triple
T12631457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyandot of Anderdon Nation |
E301650
|
entity |
| Predicate | hasHeritage |
P1494
|
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 of Anderdon Nation, hasHeritage, Huron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Huron Context triple: [Wyandot of Anderdon Nation, hasHeritage, 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.
Huron
Huron was one of the individual nuclear detonations conducted during the United States’ 1956 Operation Redwing test series in the Pacific Proving Grounds.
-
D.
St. Clair
St. Clair is a Scottish-origin surname historically associated with nobility and military and political figures in the English-speaking world.
-
E.
St. Clair
St. Clair is a township in southwestern Ontario, Canada, situated along the St. Clair River within Lambton County.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9610e4f408190946f37325d69375c |
completed | April 10, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c71482c819083d65c1a39e90e41 |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 9, 2026, 5:15 p.m.