Triple
T27975629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | میدان آزادی |
E706480
|
entity |
| Predicate | اهمیت |
P428
|
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.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
B.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
-
C.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
D.
importantAria
Indicates that an aria is considered significant or central in its musical, dramatic, or contextual role.
-
E.
significance
chosen
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
- 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_69f63b38a5c081908edb1c9a415c914b |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:41 p.m.