Triple
T8256400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesrop Mashtots Avenue, Yerevan |
E193079
|
entity |
| Predicate | toponymHonors |
P81234
|
FINISHED |
| Object | Armenian cultural heritage |
—
|
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: Armenian cultural heritage | Statement: [Mesrop Mashtots Avenue, Yerevan, toponymHonors, Armenian cultural heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymHonors Context triple: [Mesrop Mashtots Avenue, Yerevan, toponymHonors, Armenian cultural heritage]
-
A.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
B.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
C.
toponymStatus
Indicates the status or classification of a place name within a geographic naming or toponymic system.
-
D.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
E.
notablePlaceNamedAfter
Indicates that a notable place (such as a city, building, or landmark) is named in honor of or derived from the name of a particular entity.
- F. None of above. chosen
Provenance (4 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78fb91d08190904c59ccc0cd444a |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb44d1caa881909069fa925a91316b |
completed | March 31, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.