Triple
T31675190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Хорошёвская |
E808379
|
entity |
| Predicate | имеетОсвещение |
P1280
|
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.
hasLumen
Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
-
B.
featuresLightingBy
Indicates that something includes or showcases lighting created, provided, or designed by a specified entity.
-
C.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
E.
lightingRequirement
Indicates the level or type of light that is needed for something to function, grow, or be used properly.
- 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_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 11:02 p.m.