Triple
T31424043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamu Township |
E801610
|
entity |
| Predicate | hasBorderTownInIndia |
P85285
|
FINISHED |
| Object | Moreh |
—
|
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 | Statement: [Tamu Township, hasBorderTownInIndia, Moreh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTownInIndia Context triple: [Tamu Township, hasBorderTownInIndia, Moreh]
-
A.
hasBorderTownOnIndianSide
chosen
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
B.
hasBorderTownOnNepaliSide
Indicates that a location has a corresponding town situated on the Nepali side of an international border.
-
C.
borderingIndianStates
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
-
D.
hasBorderTownOnMyanmarSide
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
E.
borderingUnionTerritory
Indicates that one entity shares a land or maritime boundary with a specified Union Territory.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 30, 2026, 8:51 p.m.