Triple
T32547448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monkwearmouth Station Museum |
E831882
|
entity |
| Predicate | railwayStationOpeningDate |
P14462
|
FINISHED |
| Object | 1848 |
—
|
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: 1848 | Statement: [Monkwearmouth Station Museum, railwayStationOpeningDate, 1848]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayStationOpeningDate Context triple: [Monkwearmouth Station Museum, railwayStationOpeningDate, 1848]
-
A.
railwayStationOpened
chosen
Indicates that a railway station began operation or was officially opened on a specified date or in a specified time period.
-
B.
railwaySectionOpeningDate
Indicates the date on which a specific section of a railway line was officially opened for operation.
-
C.
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).
-
D.
railwayStationClosureDate
Indicates the date on which a railway station was officially closed to service or operations.
-
E.
railwayOpeningPeriod
Indicates the time span during which a railway line or station was officially opened and in operation.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:02 a.m.