Triple
T24522920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Boma |
E606583
|
entity |
| Predicate | distanceToMouthOfCongoRiver |
P156599
|
FINISHED |
| Object | approximately 100 km upstream |
—
|
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: approximately 100 km upstream | Statement: [Port of Boma, distanceToMouthOfCongoRiver, approximately 100 km upstream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMouthOfCongoRiver Context triple: [Port of Boma, distanceToMouthOfCongoRiver, approximately 100 km upstream]
-
A.
distanceToKinshasa
Indicates the measured spatial distance between a given entity’s location and the city of Kinshasa.
-
B.
distanceFromBangui
Indicates the measured distance between a given location and the city of Bangui.
-
C.
distanceFromVictoriaFalls
Indicates the measured distance between a given location and Victoria Falls.
-
D.
approximateDistanceToBangui
Indicates that one entity has an estimated or rough distance measurement relative to the location of Bangui.
-
E.
distanceFromAtlanticMouthOfAmazon
Indicates the measured distance of something from the point where the Amazon River meets the Atlantic Ocean.
- F. None of above. chosen
Provenance (4 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:25 a.m.