Triple
T15388492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firozkoh |
E367974
|
entity |
| Predicate | hasHistoricalRegion |
P915
|
FINISHED |
| Object | Ghor |
E139113
|
NE 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: Ghor | Statement: [Firozkoh, hasHistoricalRegion, Ghor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ghor Context triple: [Firozkoh, hasHistoricalRegion, Ghor]
-
A.
Ghor
Ghor is a low-lying, fertile region within the Jordan Rift Valley known for its agricultural lands and proximity to the Jordan River.
-
B.
Ghor Province
chosen
Ghor Province is a mountainous, centrally located region of Afghanistan known for its remote terrain, historical significance, and ethnically diverse population.
-
C.
Ghorband
Ghorband is a notable town in Afghanistan’s Parwan Province, known for its location in a fertile valley northwest of Kabul.
-
D.
Khar
Khar is a town in northwestern Pakistan that serves as the administrative and commercial center of the Bajaur region in Khyber Pakhtunkhwa.
-
E.
Khar
Khar is a suburban neighborhood in Mumbai, India, known for its residential areas, shopping streets, and proximity to the Arabian Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f2754648190bfd0bd15f20b40d2 |
completed | May 9, 2026, 4:21 p.m. |
Created at: April 10, 2026, 3:19 a.m.