Triple
T10982954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elektrozavodskaya (Bolshaya Koltsevaya Line) |
E259553
|
entity |
| Predicate | hasModernDesign |
P49135
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Elektrozavodskaya (Bolshaya Koltsevaya Line), hasModernDesign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernDesign Context triple: [Elektrozavodskaya (Bolshaya Koltsevaya Line), hasModernDesign, true]
-
A.
isModern
chosen
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
B.
hasModernMaterial
Indicates that an entity incorporates or is made from contemporary, recently developed, or non-traditional materials.
-
C.
isModernStructure
Indicates that a structure is contemporary in design, construction, or style, typically reflecting recent architectural methods or aesthetics.
-
D.
hasModernSquare
Indicates that an entity possesses or includes a square-shaped feature designed or styled in a modern way.
-
E.
isModernistCity
Indicates that a city embodies characteristics of modernist urban design, architecture, and planning principles.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772eb518c8190a885a417815f2ff6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.