Triple
T23167902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Upper Nile |
E578761
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Bor |
—
|
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: Bor | Statement: [Greater Upper Nile, hasMajorCity, Bor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bor Context triple: [Greater Upper Nile, hasMajorCity, Bor]
-
A.
Bor
chosen
Bor is a major town in South Sudan’s Jonglei State, situated on the White Nile and serving as an important regional administrative and transport hub.
-
B.
Bor
Bor is a town in Nizhny Novgorod Oblast, Russia, located on the left bank of the Volga River opposite the city of Nizhny Novgorod and known for its industrial and river transport significance.
-
C.
Bor
Bor is a London Underground station serving the Borough area of Southwark in central London.
-
D.
Bor
Bor is a small town in the Plzeň Region of the Czech Republic, known for its historic architecture and surrounding rural landscape.
-
E.
Bor
Bor is a mining town in eastern Serbia known for its large copper deposits and heavy industry.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2d51288190af0d5747090d8e5d |
completed | April 29, 2026, 4:55 a.m. |
Created at: April 17, 2026, 4:03 p.m.