Triple
T30366180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India and Myanmar |
E772426
|
entity |
| Predicate | hasBorderStatesOnIndianSide |
P85007
|
FINISHED |
| Object | Arunachal Pradesh |
—
|
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: Arunachal Pradesh | Statement: [India and Myanmar, hasBorderStatesOnIndianSide, Arunachal Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderStatesOnIndianSide Context triple: [India and Myanmar, hasBorderStatesOnIndianSide, Arunachal Pradesh]
-
A.
borderingIndianStates
chosen
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
-
B.
hasBorderTownOnIndianSide
Indicates that a location has a corresponding town situated on the Indian side of an international border.
-
C.
borderingUnionTerritory
Indicates that one entity shares a land or maritime boundary with a specified Union Territory.
-
D.
memberStatesShareBorderAlong
Indicates that two member states have a common boundary running along a specified geographic feature or segment.
-
E.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 29, 2026, 7:58 p.m.