Triple
T13803236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilorin East |
E331692
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Iponrin |
E306864
|
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: Iponrin | Statement: [Ilorin East, hasSettlement, Iponrin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iponrin Context triple: [Ilorin East, hasSettlement, Iponrin]
-
A.
Iponri
chosen
Iponri is a residential and commercial neighborhood in Lagos, Nigeria, situated within the Surulere area and known for its markets and proximity to major city routes.
-
B.
Riniken
Riniken is a small municipality in the canton of Aargau in northern Switzerland, situated near the town of Brugg.
-
C.
Shinrone
Shinrone is a small village in County Offaly, Ireland, known for its rural character and historic parish community.
-
D.
Moruya
Moruya is a coastal town in New South Wales, Australia, known for its scenic river setting, nearby beaches, and historic granite quarries.
-
E.
Poronin
Poronin is a village in southern Poland’s Tatra region, known as a gateway to the Tatra Mountains and a base for tourism near Zakopane.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026c36108190a7436034a730a261 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b08bd7c48190bcdf110ccd27c003 |
completed | May 3, 2026, 8:31 p.m. |
Created at: April 9, 2026, 10:12 p.m.