Triple
T24056601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سعدی شیرازی |
E595823
|
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.
geographicalEffect
Indicates how one geographical feature, condition, or event influences or alters another in terms of physical, environmental, or spatial characteristics.
-
B.
geographicalReality
Indicates that something pertains to, reflects, or is constrained by actual physical geography or spatial conditions in the real world.
-
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.
geographyBehavior
Indicates how an entity behaves, functions, or interacts in relation to its geographic context or location.
-
E.
geographicContext
chosen
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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:32 p.m.