Triple
T30016819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samtse District |
E762617
|
entity |
| Predicate | hasNeighboringCountryRegion |
P17964
|
FINISHED |
| Object | Indian state of West Bengal |
—
|
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: Indian state of West Bengal | Statement: [Samtse District, hasNeighboringCountryRegion, Indian state of West Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringCountryRegion Context triple: [Samtse District, hasNeighboringCountryRegion, Indian state of West Bengal]
-
A.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
B.
neighboringCountryPresence
Indicates that one country has a geographic presence (such as territory, bases, or influence) in or immediately adjacent to a neighboring country.
-
C.
borderingCountryOfRegion
Indicates that a country shares a land or maritime border with a specified geographic region.
-
D.
neighboringRegion
chosen
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
E.
hasEconomicRegionAlongBorder
Indicates that two entities share a border along which a defined economic region or zone exists or is recognized.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 29, 2026, 6:46 p.m.