Triple
T1362998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congo River |
E29137
|
entity |
| Predicate | navigationObstacle |
P22896
|
FINISHED |
| Object | rapids near Matadi |
—
|
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: rapids near Matadi | Statement: [Congo River, navigationObstacle, rapids near Matadi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationObstacle Context triple: [Congo River, navigationObstacle, rapids near Matadi]
-
A.
hasNavigationHazard
chosen
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
-
B.
hasNavigationHazardRelevance
Indicates that something is relevant to, affected by, or poses a potential hazard to navigation.
-
C.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
D.
navigationClearanceType
Indicates the specific type or category of clearance granted for a navigation-related operation or movement.
-
E.
navigationCondition
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b4ab3c8190ad692e32eee05976 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.