Triple
T16092106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marunouchi Line |
E390381
|
entity |
| Predicate | completionDateMainLine |
P121866
|
FINISHED |
| Object | 1962-03-23 |
—
|
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: 1962-03-23 | Statement: [Marunouchi Line, completionDateMainLine, 1962-03-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionDateMainLine Context triple: [Marunouchi Line, completionDateMainLine, 1962-03-23]
-
A.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
B.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
C.
cuttingCompletionDate
Indicates the date on which a cutting process or operation is completed.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
substantialCompletionDate
Indicates the date on which a project, work, or obligation is considered substantially complete, meaning the main required work has been finished to the point it can be used for its intended purpose.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:59 a.m.