Triple
T35618901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shigaraki Kōgen Railway |
E1029253
|
entity |
| Predicate | tookOverOperationYear |
P9945
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Shigaraki Kōgen Railway, tookOverOperationYear, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOverOperationYear Context triple: [Shigaraki Kōgen Railway, tookOverOperationYear, 1987]
-
A.
takenOverInYear
chosen
Indicates that one entity assumed control or ownership of another entity in a specified calendar year.
-
B.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
C.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
D.
operatedInYear
Indicates that an entity was actively operating or functioning during a specified year.
-
E.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.