Triple
T32861427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | شهرستان پیشوا |
E840526
|
entity |
| Predicate | منطقه جغرافیایی |
P171825
|
FINISHED |
| Object | شمال ایران |
—
|
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: شمال ایران | Statement: [شهرستان پیشوا, منطقه جغرافیایی, شمال ایران]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: منطقه جغرافیایی Context triple: [شهرستان پیشوا, منطقه جغرافیایی, شمال ایران]
-
A.
ردهٔجغرافیایی
Indicates a geographical classification or categorization relationship between entities based on their location or spatial grouping.
-
B.
جهت جغرافیایی
chosen
Indicates the spatial or compass direction in which one entity is oriented or located relative to another.
-
C.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
D.
geographicalEffect
Indicates how one geographical feature, condition, or event influences or alters another in terms of physical, environmental, or spatial characteristics.
-
E.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ceb729fc81908ef924d90de729f1 |
completed | May 3, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_69f6cc177b288190904f3f23cb856d8b |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.