Triple
T29648574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamu |
E756071
|
entity |
| Predicate | borderWithIndianTown |
P85285
|
FINISHED |
| Object | Moreh, Manipur |
—
|
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: Moreh, Manipur | Statement: [Tamu, borderWithIndianTown, Moreh, Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderWithIndianTown Context triple: [Tamu, borderWithIndianTown, Moreh, Manipur]
-
A.
hasBorderTownOnIndianSide
chosen
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
B.
borderWithTerritory
Indicates that one territory shares a common boundary or border with another territory.
-
C.
borderTypeWithBangladesh
Indicates the type or nature of the border relationship that an entity shares with Bangladesh.
-
D.
borderTypeWithNepal
Indicates the specific nature or classification of the border relationship that an entity shares with Nepal.
-
E.
hasBorderTownOnNepaliSide
Indicates that a location has a corresponding town situated on the Nepali side of an international 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 28, 2026, 6:51 p.m.