Triple
T29264123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botchan Ressha |
E741928
|
entity |
| Predicate | originalOperationEnd |
P200179
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Botchan Ressha, originalOperationEnd, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalOperationEnd Context triple: [Botchan Ressha, originalOperationEnd, 1954]
-
A.
originalRunEndOfWork
Indicates that a given run or process marks the final or concluding point of a particular piece of work.
-
B.
endOfUsefulOperations
Indicates that the useful or intended operations of an entity, process, or system have been completed or can no longer be effectively performed.
-
C.
ceasedOperationAfter
Indicates that one entity stopped functioning, operating, or being active after another specified event or entity’s operation ended.
-
D.
finalOperations
Indicates that an entity is involved in the last or concluding set of actions or processes within a sequence or workflow.
-
E.
operationalStatusAtEnd
Indicates the final operational condition or state of an entity at the conclusion of a specified period or process.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
| PDg | Predicate description generation | batch_69ff79e645c08190a974b5239efac35b |
completed | May 9, 2026, 6:16 p.m. |
Created at: April 28, 2026, 12:43 p.m.