Triple
T20066649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niavaran neighborhood |
E499623
|
entity |
| Predicate | hasPropertyValueLevel |
P23698
|
FINISHED |
| Object | high real estate prices |
—
|
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: high real estate prices | Statement: [Niavaran neighborhood, hasPropertyValueLevel, high real estate prices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyValueLevel Context triple: [Niavaran neighborhood, hasPropertyValueLevel, high real estate prices]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
hasLevelType
Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
-
C.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
D.
hasLocalLevel
Indicates that one entity possesses, is associated with, or is defined at a specific local administrative or organizational level relative to another entity.
-
E.
hasLevelNumber
Indicates that an entity is associated with a specific level identified by a numerical value.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66379f2cc81908f13a7b216878f12 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.