Triple
T26726131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province No. 2, Nepal |
E673839
|
entity |
| Predicate | hasImportantBorderTown |
P15361
|
FINISHED |
| Object | Birgunj |
—
|
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 | Statement: [Province No. 2, Nepal, hasImportantBorderTown, Birgunj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantBorderTown Context triple: [Province No. 2, Nepal, hasImportantBorderTown, Birgunj]
-
A.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
B.
hasNotableBuildingOnBorder
Indicates that a notable or significant building is located directly on or straddling the border between two areas or entities.
-
C.
hasBorderCity
chosen
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
D.
isBorderTownBetween
Indicates that a town is located on or near the boundary separating two specified regions, serving as a border settlement between them.
-
E.
isInBorderTown
Indicates that an entity is located in a town situated on or very near a political or geographic border.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:42 a.m.