Triple
T31399303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | هندوکش شرقی |
E800948
|
entity |
| Predicate | بخش شرقی |
P41303
|
FINISHED |
| Object | رشتهکوه هندوکش |
—
|
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: رشتهکوه هندوکش | Statement: [هندوکش شرقی, بخش شرقی, رشتهکوه هندوکش]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: بخش شرقی Context triple: [هندوکش شرقی, بخش شرقی, رشتهکوه هندوکش]
-
A.
regionalCenterOfEasternSide
Indicates that an entity functions as the primary administrative or functional center for the eastern part of a larger region or area.
-
B.
easternSegmentOrientation
Indicates the directional orientation of the eastern segment of an object or structure relative to a reference frame.
-
C.
locatedInEasternPartOf
chosen
Indicates that one entity is situated within the eastern portion or region of another entity.
-
D.
easternProvince
Indicates that one region or administrative unit is located to the east of another within the same broader territory or country.
-
E.
easternContinuationLeadsTo
Indicates that a path, route, or extension continues eastward from a given point and leads to another location or state.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.