Triple
T1468655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab-el-Mandeb Strait |
E27082
|
entity |
| Predicate | easternChannelWidth |
P25021
|
FINISHED |
| Object | about 3 kilometers |
—
|
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: about 3 kilometers | Statement: [Bab-el-Mandeb Strait, easternChannelWidth, about 3 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternChannelWidth Context triple: [Bab-el-Mandeb Strait, easternChannelWidth, about 3 kilometers]
-
A.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
-
B.
maximumChannelWidth
chosen
Indicates the greatest allowable or observed width of a channel in the given context.
-
C.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d70a948190b50a6c1b36abc740 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.