Triple
T13844898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbatskaya |
E332773
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Moscow |
E1747
|
NE 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: Moscow | Statement: [Arbatskaya, hasCity, Moscow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moscow Context triple: [Arbatskaya, hasCity, Moscow]
-
A.
Moscow
Moscow is a small borough in Lackawanna County, Pennsylvania, known as a residential community near the Scranton metropolitan area.
-
B.
Moscow
chosen
Moscow is the capital and largest city of Russia, serving as its political, economic, and cultural center.
-
C.
Moscow
Moscow is a fictional character from the Spanish television series "Money Heist" (La Casa de Papel), known as a kind-hearted, blue-collar miner and the father of Denver who participates in the Royal Mint heist.
-
D.
Mosca
Mosca is the cunning and manipulative servant in Ben Jonson’s play "Volpone," known for orchestrating deceptions and driving much of the plot’s dark comedy.
-
E.
Moscow City
Moscow City is a modern high-rise business district in western Moscow known for its cluster of skyscrapers, financial institutions, and commercial developments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b1a25c8190a9f85ba43c421188 |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8e85c6c81908bdf5d43b917d151 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:13 p.m.