Triple
T3089515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omdurman |
E64455
|
entity |
| Predicate | riverCrossingWith |
P33399
|
FINISHED |
| Object | Khartoum via bridges over the Nile |
—
|
LITERAL 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: Khartoum via bridges over the Nile | Statement: [Omdurman, riverCrossingWith, Khartoum via bridges over the Nile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossingWith Context triple: [Omdurman, riverCrossingWith, Khartoum via bridges over the Nile]
-
A.
riverCrossingConnection
chosen
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
-
B.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
C.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
D.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
E.
notableRiverCrossingRole
Indicates that an entity plays a significant role as a location or feature involved in the crossing of a river.
- F. None of above.
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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20b99a4819090c3d3e08ed556ad |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.