Triple
T31399320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | واسی |
E800949
|
entity |
| Predicate | موقعیت_جغرافیایی |
P3227
|
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.
geographicContext
chosen
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
B.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
C.
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.
-
D.
geographicRole
Indicates a relationship where one entity serves a specific geographic function, status, or role in relation to another location or area.
-
E.
geographicalReality
Indicates that something pertains to, reflects, or is constrained by actual physical geography or spatial conditions in the real world.
- 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.