Triple
T14430183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Арбатско-Покровская линия |
E357804
|
entity |
| Predicate | открыта |
P617
|
FINISHED |
| Object | 1938 год |
—
|
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: 1938 год | Statement: [Арбатско-Покровская линия, открыта, 1938 год]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: открыта Context triple: [Арбатско-Покровская линия, открыта, 1938 год]
-
A.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
-
B.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
C.
openedIn
chosen
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
D.
openedForPublic
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
-
E.
openness
Indicates that an entity is receptive, transparent, or willing to consider, share, or engage with new information, ideas, or interactions.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914570f08190b1c7c1c57a0cb476 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.