Triple
T30440305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soham railway station |
E774421
|
entity |
| Predicate | rebuildStatus |
P15976
|
FINISHED |
| Object | newly constructed station on historic line |
—
|
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: newly constructed station on historic line | Statement: [Soham railway station, rebuildStatus, newly constructed station on historic line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildStatus Context triple: [Soham railway station, rebuildStatus, newly constructed station on historic line]
-
A.
rebuildReason
Indicates the reason or justification for performing a rebuild of something (e.g., a system, structure, or component).
-
B.
reconstructionStatus
chosen
Indicates the current state or phase of a reconstruction process that an entity is undergoing or has undergone.
-
C.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
D.
rebuildType
Indicates the type or category of rebuilding or reconstruction process applied to an entity.
-
E.
majorRebuildCompleted
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6869840948190bdb374de6c9edf96 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:08 p.m.