Triple
T9461542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نورستانیان |
E228156
|
entity |
| Predicate | نوع مسکن سنتی |
P542
|
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.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container for another entity.
-
B.
traditionalHomeOf
Indicates that a place is historically or customarily regarded as the primary homeland or origin location of a particular group or culture.
-
C.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
habitation
Indicates that one entity serves as the dwelling place, residence, or living environment for another entity.
-
E.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcc8b1881908aa6ee13ab195330 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.