Triple
T12276183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aso Rock |
E292594
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Asokoro |
E66826
|
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: Asokoro | Statement: [Aso Rock, locatedIn, Asokoro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asokoro Context triple: [Aso Rock, locatedIn, Asokoro]
-
A.
Asokoro
chosen
Asokoro is an upscale residential and administrative district in Abuja, Nigeria, known for hosting many government institutions, embassies, and high-profile residents.
-
B.
Boroko
Boroko is a major residential and commercial suburb of Port Moresby in Papua New Guinea, known for its shopping areas and sports facilities.
-
C.
Tokoro
Tokoro is a coastal district of Kitami City in Hokkaido, Japan, known historically for its fishing industry and drift ice along the Sea of Okhotsk.
-
D.
Miyakoan
Miyakoan is a Ryukyuan language spoken primarily on the Miyako Islands of Japan, distinct from standard Japanese and recognized as endangered.
-
E.
Asago
Asago is a city in northern Hyōgo Prefecture, Japan, known for its mountainous scenery, historic castle ruins, and hot spring resorts.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cf06cf08190ac8671dd9bbed03d |
completed | April 10, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e6d72d081908c8697257df712f1 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:52 p.m.