Triple
T31675183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | имеетИнфраструктуруДляМГН |
P126726
|
FINISHED |
| Object | да |
—
|
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: да | Statement: [Хорошёвская, имеетИнфраструктуруДляМГН, да]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетИнфраструктуруДляМГН Context triple: [Хорошёвская, имеетИнфраструктуруДляМГН, да]
-
A.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
B.
hasInfrastructureAbove
Indicates that one entity’s infrastructure is physically located above or over another entity.
-
C.
hasInfrastructureAlong
Indicates that infrastructure is present or extends along the length or course of another entity (such as a route, boundary, or geographic feature).
-
D.
hasAccessInfrastructure
chosen
Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
-
E.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:02 p.m.