Triple
T30919295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolnicheskaya Line stations |
E787671
|
entity |
| Predicate | hasOpeningPeriod |
P181443
|
FINISHED |
| Object | from 1935 onwards |
—
|
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: from 1935 onwards | Statement: [Sokolnicheskaya Line stations, hasOpeningPeriod, from 1935 onwards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningPeriod Context triple: [Sokolnicheskaya Line stations, hasOpeningPeriod, from 1935 onwards]
-
A.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
B.
isOpeningFor
Indicates that one entity serves as the beginning, introduction, or initial act for another entity, such as an event, performance, or sequence.
-
C.
hasExtensionOpeningDate
Indicates that an entity has an associated opening date specifically for an extension or expansion of it.
-
D.
hasAwardPeriod
Indicates the time span or date range during which an award is valid, active, or applicable.
-
E.
hasOpeningCondition
Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
- F. None of above. chosen
Provenance (4 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 29, 2026, 8:51 p.m.