Triple
T15406660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongmit |
E368473
|
entity |
| Predicate | borderedByHistorically |
P93966
|
FINISHED |
| Object | other Shan principalities |
—
|
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: other Shan principalities | Statement: [Mongmit, borderedByHistorically, other Shan principalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByHistorically Context triple: [Mongmit, borderedByHistorically, other Shan principalities]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
-
C.
hasSharedBorderHistoryWith
chosen
Indicates that two entities have a history of sharing a common border or boundary at some point in time.
-
D.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
E.
isDividedByModernBorder
Indicates that a single entity or area is split into separate parts by a contemporary political or administrative boundary.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea36c6881909eaea48e9608897a |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.