Triple
T29598027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raxaul–Birgunj crossing |
E754358
|
entity |
| Predicate | hasNearbyDryPort |
P86796
|
FINISHED |
| Object | Birgunj Inland Container Depot |
—
|
NE NERFINISHED |
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: Birgunj Inland Container Depot | Statement: [Raxaul–Birgunj crossing, hasNearbyDryPort, Birgunj Inland Container Depot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyDryPort Context triple: [Raxaul–Birgunj crossing, hasNearbyDryPort, Birgunj Inland Container Depot]
-
A.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
B.
hasNearbyPortCountry
Indicates that one entity is a country that has a seaport located geographically close to the other entity.
-
C.
hasNearbyFerryPort
Indicates that one location is situated close enough to another location that serves as a ferry port to be considered nearby.
-
D.
nearbyPortFacility
chosen
Indicates that one entity is located close to or in the immediate vicinity of a port facility.
-
E.
isMainDeepWaterPortFor
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 28, 2026, 6:19 p.m.