Triple
T30366184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India and Myanmar |
E772426
|
entity |
| Predicate | hasBorderStatesOnMyanmarSide |
P191356
|
FINISHED |
| Object | Kachin State |
—
|
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: Kachin State | Statement: [India and Myanmar, hasBorderStatesOnMyanmarSide, Kachin State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderStatesOnMyanmarSide Context triple: [India and Myanmar, hasBorderStatesOnMyanmarSide, Kachin State]
-
A.
hasBorderTownOnMyanmarSide
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
B.
hasInternationalBoundaryLengthWithMyanmar
Indicates the measured length of the international land or maritime boundary shared between a given entity and Myanmar.
-
C.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
D.
borderTypeWithMyanmar
Indicates the specific nature or classification of the border relationship that an entity has with Myanmar.
-
E.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
- F. None of above. chosen
Provenance (4 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 29, 2026, 7:58 p.m.