Triple
T26690570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sino-Nepalese Treaty of Peace and Friendship |
E672866
|
entity |
| Predicate | borderStates |
P80398
|
FINISHED |
| Object | Tibet Autonomous Region |
—
|
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: Tibet Autonomous Region | Statement: [Sino-Nepalese Treaty of Peace and Friendship, borderStates, Tibet Autonomous Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStates Context triple: [Sino-Nepalese Treaty of Peace and Friendship, borderStates, Tibet Autonomous Region]
-
A.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
B.
borderingOpposingState
Indicates that one state shares a border with another state that is politically, militarily, or ideologically opposed to it.
-
C.
borderStateOf
chosen
Indicates that one state shares a common boundary or border with another state.
-
D.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
-
E.
USStateBorderFor
Indicates that a U.S. state serves as a bordering state for the specified geographic or political 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 3:25 a.m.