Triple
T30485567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nangbeto Dam |
E775708
|
entity |
| Predicate | crossBorderProject |
P179821
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nangbeto Dam, crossBorderProject, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderProject Context triple: [Nangbeto Dam, crossBorderProject, yes]
-
A.
crossBorderAgglomerationWith
Indicates a relationship where economic or spatial clustering of activities spans or connects across a national or regional border between the linked entities.
-
B.
crossBorderSection
Indicates a section or segment that extends across or passes from one jurisdiction, region, or country into another.
-
C.
crossBorderGatewayFor
Indicates that one entity functions as a gateway enabling traffic or interaction to cross a border or boundary for another entity.
-
D.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
E.
crossBorderTradeHub
Indicates a location or entity that serves as a central point for facilitating, coordinating, or processing trade activities that occur across national or regional borders.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 29, 2026, 8:13 p.m.