Triple
T14474097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banjul International Airport |
E358923
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Yundum |
E970645
|
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: Yundum | Statement: [Banjul International Airport, locatedIn, Yundum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yundum Context triple: [Banjul International Airport, locatedIn, Yundum]
-
A.
Yundum
chosen
Yundum is a town in The Gambia known for its international airport and proximity to the capital, Banjul.
-
B.
Yenda
Yenda is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural production, particularly viticulture and horticulture.
-
C.
Kunda
Kunda is a small industrial town in northern Estonia known for its cement industry and archaeological significance.
-
D.
Yunyarinyi
Yunyarinyi is a small remote Aboriginal community in the Anangu Pitjantjatjara Yankunytjatjara (APY) Lands of northern South Australia.
-
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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91fc1fc48190842b09aa03ba79f8 |
completed | April 14, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd649e103c81908001b45c16d1fd79 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:20 a.m.