Triple
T10933175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghulam Khan |
E258259
|
entity |
| Predicate | nearbyCountryRegion |
P17964
|
FINISHED |
| Object | southeastern Afghanistan |
—
|
LITERAL FINISHED |
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: southeastern Afghanistan | Statement: [Ghulam Khan, nearbyCountryRegion, southeastern Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCountryRegion Context triple: [Ghulam Khan, nearbyCountryRegion, southeastern Afghanistan]
-
A.
nearbyCountryProvince
Indicates that a province is geographically close to, or shares a border with, a specified country.
-
B.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
C.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
D.
neighboringRegion
chosen
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
E.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770a16cbc8190acd619defed7114c |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.