Triple
T26888490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naberezhnaya Reki Moyki 12 |
E677106
|
entity |
| Predicate | hasPushkinMuseumName |
P34311
|
FINISHED |
| Object | Pushkin Apartment Museum on the Moika |
—
|
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: Pushkin Apartment Museum on the Moika | Statement: [Naberezhnaya Reki Moyki 12, hasPushkinMuseumName, Pushkin Apartment Museum on the Moika]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPushkinMuseumName Context triple: [Naberezhnaya Reki Moyki 12, hasPushkinMuseumName, Pushkin Apartment Museum on the Moika]
-
A.
hasMuseumName
chosen
Indicates that an entity (typically a museum) is associated with a specific name or title.
-
B.
hasMemorialMuseum
Indicates that a memorial museum is dedicated to, associated with, or established in honor of a particular entity.
-
C.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
-
D.
hasMuseumAt
Indicates that a museum is located at or exists in a specified place or location.
-
E.
hasParkNamedAfter
Indicates that one entity has a park that is named in honor of, or after, 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 5:43 a.m.