Triple
T22934027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uma |
E569526
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Koro |
—
|
NE NERFINISHED |
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: Koro | Statement: [Uma, hasAlternativeName, Koro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koro Context triple: [Uma, hasAlternativeName, Koro]
-
A.
Koro
Koro is a volcanic island in Fiji’s Lomaiviti archipelago, known for its rugged terrain, traditional villages, and surrounding coral reefs.
-
B.
Koro
Koro is a town and commune in central Mali known as a local administrative and trading center within the Mopti Region.
-
C.
Koro Uma
chosen
Koro Uma is an alternate name for the Uma language, an Austronesian language spoken in Central Sulawesi, Indonesia.
-
D.
Koro Wachi
Koro Wachi is a lesser-known Plateau language spoken in central Nigeria, notable for its place within the Benue–Congo branch of the Niger–Congo language family.
-
E.
Kogarah
Kogarah is a suburb in southern Sydney, New South Wales, Australia, known as a residential and commercial hub in the St George area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18134484c8190b7311606c17d058d |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:44 p.m.