Triple
T34933490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amritsar division |
E1007504
|
entity |
| Predicate | borderingInternationalBoundary |
P137050
|
FINISHED |
| Object | India–Pakistan border |
—
|
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–Pakistan border | Statement: [Amritsar division, borderingInternationalBoundary, India–Pakistan border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingInternationalBoundary Context triple: [Amritsar division, borderingInternationalBoundary, India–Pakistan border]
-
A.
bordersInternationalBoundary
chosen
Indicates that one entity shares an international boundary line directly with another sovereign entity.
-
B.
nationalBorder
Indicates that two geographic or political entities share a common national boundary separating their territories.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
countyBorder
Indicates that two counties share a common boundary or border with each other.
-
E.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4 p.m.