Triple
T2223435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolshaya Koltsevaya Line |
E48192
|
entity |
| Predicate | officialCompletionDate |
P2818
|
FINISHED |
| Object | 2023-03-01 |
—
|
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: 2023-03-01 | Statement: [Bolshaya Koltsevaya Line, officialCompletionDate, 2023-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialCompletionDate Context triple: [Bolshaya Koltsevaya Line, officialCompletionDate, 2023-03-01]
-
A.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
D.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
E.
concludedAt
chosen
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03d1df88190950c691a4c246bd1 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.