Triple
T3698633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinshasa–Brazzaville metropolitan area |
E78518
|
entity |
| Predicate | riverCrossingType |
P33399
|
FINISHED |
| Object | ferry connections |
—
|
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: ferry connections | Statement: [Kinshasa–Brazzaville metropolitan area, riverCrossingType, ferry connections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossingType Context triple: [Kinshasa–Brazzaville metropolitan area, riverCrossingType, ferry connections]
-
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.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
D.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
E.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc512ba188190a15bcacafac3f476 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.