Triple
T35351971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bashgal River |
E1020904
|
entity |
| Predicate | valleyInhabitedBy |
P6481
|
FINISHED |
| Object | Nuristani peoples |
—
|
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: Nuristani peoples | Statement: [Bashgal River, valleyInhabitedBy, Nuristani peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyInhabitedBy Context triple: [Bashgal River, valleyInhabitedBy, Nuristani peoples]
-
A.
inhabitedBy
chosen
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
B.
valleyLocation
Indicates that one entity is located in, at, or within the geographic bounds of a valley relative to another entity or context.
-
C.
valleyUsedBy
Indicates that a valley is utilized or traversed by a particular entity, such as for passage, habitation, or other activities.
-
D.
locatedInRiverValley
Indicates that something is situated within the geographical area of a river valley.
-
E.
valleyKnownFor
Indicates that a particular valley is widely recognized or notable for a specific feature, product, activity, or characteristic.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.