Triple
T27976013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سرخپوشان |
E706491
|
entity |
| Predicate | کاربرد جغرافیایی |
P150084
|
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.
geographicalPractice
Indicates a relationship where an entity engages in or is associated with a practice, activity, or method that is specific to or characteristic of a particular geographic area or location.
-
B.
geographicalEffect
Indicates how one geographical feature, condition, or event influences or alters another in terms of physical, environmental, or spatial characteristics.
-
C.
geographicalReality
Indicates that something pertains to, reflects, or is constrained by actual physical geography or spatial conditions in the real world.
-
D.
geographicalUsage
chosen
Indicates that something is used, applied, or occurs within a particular geographic area or region.
-
E.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 7:41 p.m.