Triple
T10383774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tateyama Kurobe Alpine Route |
E244706
|
entity |
| Predicate | typicallyOpenFromMonth |
P93895
|
FINISHED |
| Object | April |
—
|
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: April | Statement: [Tateyama Kurobe Alpine Route, typicallyOpenFromMonth, April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOpenFromMonth Context triple: [Tateyama Kurobe Alpine Route, typicallyOpenFromMonth, April]
-
A.
temporarilyClosedFrom
Indicates that an entity is not accessible or operating for a specific, limited time period starting from a given point.
-
B.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
C.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
D.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
E.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a2aafc8190aa11d14852fa1599 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:04 p.m.