Triple
T5322414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algoma District |
E121704
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Wawa |
E133963
|
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: Wawa | Statement: [Algoma District, hasSettlement, Wawa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wawa Context triple: [Algoma District, hasSettlement, Wawa]
-
A.
Wawa
chosen
Wawa is a small town in northern Ontario, Canada, known for its iconic giant Canada goose statue and its history as a mining and forestry community.
-
B.
Wanze
Wanze is a municipality in eastern Belgium situated along the Meuse River in the Walloon Region.
-
C.
Washo
Washo is a Native American language isolate traditionally spoken by the Washoe people of the Lake Tahoe region in California and Nevada.
-
D.
Zumwa
Zumwa is the Gbagyi-language name for Zuma Rock, the iconic monolithic inselberg near Abuja, Nigeria.
-
E.
Yassa
Yassa was the codified legal and administrative code traditionally attributed to Genghis Khan that governed the Mongol Empire and its successor states.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8577ba3881909a28cbf744648256 |
completed | March 20, 2026, 5:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf18a836988190b7baf3c24fea6f03 |
completed | March 21, 2026, 10:16 p.m. |
Created at: March 20, 2026, 1:59 p.m.