Triple
T21908597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathu La Pass |
E541003
|
entity |
| Predicate | reopenedForTrade |
P59082
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Nathu La Pass, reopenedForTrade, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedForTrade Context triple: [Nathu La Pass, reopenedForTrade, 2006]
-
A.
openedForTrade
Indicates that an entity has begun allowing commercial transactions or trading activities to occur.
-
B.
reopenedFor
chosen
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
C.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
D.
reopensIn
Indicates that an entity resumes operation or becomes accessible again at a specified time or under specified conditions after having been closed or inactive.
-
E.
reopenedBy
Indicates that a previously closed or resolved item, case, or process has been opened again by a specific agent or entity.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121d8c3108190a178ec6b3857da3f |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:39 p.m.