Triple
T34304617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese national expressway network |
E880272
|
entity |
| Predicate | firstMajorRouteOpeningYear |
P58725
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Japanese national expressway network, firstMajorRouteOpeningYear, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorRouteOpeningYear Context triple: [Japanese national expressway network, firstMajorRouteOpeningYear, 1963]
-
A.
firstMajorRouteOpenedIn
chosen
Indicates the date or time when an entity’s first major route was officially opened or began operation.
-
B.
firstMajorRouteOpenedBy
Indicates that one entity is the first major route that was opened or established by another entity.
-
C.
firstSubwayOpeningDate
Indicates the calendar date on which a subway system or line first began operating.
-
D.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
E.
firstMajorRunYear
Indicates the year in which something (such as an event, production, or operation) first began its major or primary run.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.