Triple
T26962452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birtamode |
E679081
|
entity |
| Predicate | borderingCountryInfluence |
P185933
|
FINISHED |
| Object | India |
—
|
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: India | Statement: [Birtamode, borderingCountryInfluence, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingCountryInfluence Context triple: [Birtamode, borderingCountryInfluence, India]
-
A.
borderingStateInfluence
Indicates that one state exerts political, economic, social, or security-related influence on another state with which it shares a land or maritime border.
-
B.
borderingCountryContext
Indicates that one country shares a land or maritime boundary with another within a specified geopolitical or temporal context.
-
C.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
D.
geographicallyBorders
Indicates that two geographic entities share a common boundary or border.
-
E.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 27, 2026, 6:32 a.m.