Triple
T2331602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbatsko–Pokrovskaya Line |
E44213
|
entity |
| Predicate | hasOpeningYear |
P19145
|
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: [Arbatsko–Pokrovskaya Line, hasOpeningYear, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningYear Context triple: [Arbatsko–Pokrovskaya Line, hasOpeningYear, 1938]
-
A.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
C.
firstRunningYear
chosen
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
D.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
E.
incorporationYear
Indicates the calendar year in which an organization or entity was formally incorporated or legally established.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.