Triple
T8342549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōbu Line Rapid |
E195954
|
entity |
| Predicate | openedAsRapidService |
P6141
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Sōbu Line Rapid, openedAsRapidService, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRapidService Context triple: [Sōbu Line Rapid, openedAsRapidService, 1960s]
-
A.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
B.
openedForServiceOnLine
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service line.
-
C.
openedAs
chosen
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
openedAsMetraService
Indicates that a transportation facility or line began operating specifically as part of the Metra commuter rail service.
-
E.
openedAsHighSpeed
Indicates that something was inaugurated or began operation specifically as a high-speed service or facility.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fe9efec81908e0c9ded3963bac5 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:58 p.m.