Triple
T14064598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preobrazhenskaya Ploshchad |
E338432
|
entity |
| Predicate | servesPartOfCity |
P3936
|
FINISHED |
| Object | northeastern Moscow |
—
|
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: northeastern Moscow | Statement: [Preobrazhenskaya Ploshchad, servesPartOfCity, northeastern Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPartOfCity Context triple: [Preobrazhenskaya Ploshchad, servesPartOfCity, northeastern Moscow]
-
A.
servesPartOf
Indicates that one entity functions as a service or provider that operates within, or as a component of, another larger system or context.
-
B.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
-
C.
partOfMetropolitanArea
Indicates that one place is included within and belongs to the larger metropolitan area of another place.
-
D.
servedCity
chosen
Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
-
E.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5689c7f48190a47ca94eaa8a9ef9 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.