Triple
T36620716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bir Tawil |
E904027
|
entity |
| Predicate | closestBodyOfWater |
P47449
|
FINISHED |
| Object | Red Sea (to the east, outside the territory) |
—
|
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: Red Sea (to the east, outside the territory) | Statement: [Bir Tawil, closestBodyOfWater, Red Sea (to the east, outside the territory)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestBodyOfWater Context triple: [Bir Tawil, closestBodyOfWater, Red Sea (to the east, outside the territory)]
-
A.
nearestLargeBodyOfWater
chosen
Indicates the closest significant body of water in proximity to a given location or entity.
-
B.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
C.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
D.
nearestCityAcrossWater
Indicates that one city is the closest city to another city when considering only routes or separation across a body of water.
-
E.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:11 p.m.