Triple
T18652899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Батьківщина-Мати |
E455984
|
entity |
| Predicate | viewingPlatform |
P13017
|
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: [Батьківщина-Мати, viewingPlatform, оглядовий майданчик у короні]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingPlatform Context triple: [Батьківщина-Мати, viewingPlatform, оглядовий майданчик у короні]
-
A.
viewTechnology
Indicates that an entity observes, inspects, or examines a particular technology.
-
B.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
C.
visualTechnology
Indicates a relationship where one entity is a technology used to capture, process, display, or otherwise handle visual information for another entity or context.
-
D.
platformShowcased
Indicates that a platform is prominently presented or highlighted, typically to draw attention to its features, capabilities, or offerings.
-
E.
hasViewingPlatform
chosen
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5501279d08190aeca36df89fee2b2 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.