Triple
T26622152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeghishe Charents |
E668227
|
entity |
| Predicate | memorialMuseum |
P15779
|
FINISHED |
| Object | Yeghishe Charents House-Museum in Yerevan |
—
|
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: Yeghishe Charents House-Museum in Yerevan | Statement: [Yeghishe Charents, memorialMuseum, Yeghishe Charents House-Museum in Yerevan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialMuseum Context triple: [Yeghishe Charents, memorialMuseum, Yeghishe Charents House-Museum in Yerevan]
-
A.
hasMemorialMuseum
chosen
Indicates that a memorial museum is dedicated to, associated with, or established in honor of a particular entity.
-
B.
nationalMuseum
Indicates that an entity functions as a primary, officially recognized museum representing a nation at the national level.
-
C.
museumOrSite
Indicates that one entity is a museum or cultural/historical site associated with or relevant to another entity.
-
D.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
E.
purposeOfMuseum
Indicates that a specified purpose or function is attributed to a particular museum.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 2:21 a.m.