Triple
T29264122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botchan Ressha |
E741928
|
entity |
| Predicate | originalOperationStart |
P3267
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [Botchan Ressha, originalOperationStart, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalOperationStart Context triple: [Botchan Ressha, originalOperationStart, 1888]
-
A.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
B.
trialOperationsBegan
Indicates that the operational phase of a trial has started.
-
C.
originalRunStartOfWork
Indicates that the referenced time or event marks the initial, unmodified starting point of a particular work activity or process.
-
D.
operatorStart
Indicates the point in time or event at which an operator begins performing an action or process.
-
E.
originalNetworkRunStart
Indicates the time or event at which a network process, operation, or run was first initiated.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 28, 2026, 12:43 p.m.