Triple
T29648572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamu |
E756071
|
entity |
| Predicate | hasBorderStatePartner |
P37800
|
FINISHED |
| Object | 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: Manipur | Statement: [Tamu, hasBorderStatePartner, Manipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderStatePartner Context triple: [Tamu, hasBorderStatePartner, Manipur]
-
A.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
-
B.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
C.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
-
D.
memberStateBorderOf
Indicates that a political subdivision or member state shares a boundary with a specified larger political entity or organization.
-
E.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 28, 2026, 6:51 p.m.