Triple
T23288934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korea–Russia border |
E589971
|
entity |
| Predicate | openedRailBridgeYear |
P29447
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [North Korea–Russia border, openedRailBridgeYear, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedRailBridgeYear Context triple: [North Korea–Russia border, openedRailBridgeYear, 1959]
-
A.
originalBridgeOpened
chosen
Indicates that the first or initial version of a bridge was opened for use or put into operation.
-
B.
railwayOpenedWith
Indicates that a railway line or section was inaugurated and began operation together with a specified associated element (such as a station, segment, or service).
-
C.
railTunnelOpeningYear
Indicates the calendar year in which a rail tunnel was officially opened for use.
-
D.
railwaySectionOpeningDate
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
E.
currentBridgeConstructionStart
Indicates the date or time at which the currently ongoing bridge construction project began.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19649570c8190b565fafa55b1f886 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:01 p.m.