Triple
T23800460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalston Kingsland railway station |
E588656
|
entity |
| Predicate | preGroup |
P153602
|
FINISHED |
| Object | British Rail |
—
|
NE NERFINISHED |
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: British Rail | Statement: [Dalston Kingsland railway station, preGroup, British Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preGroup Context triple: [Dalston Kingsland railway station, preGroup, British Rail]
-
A.
preGrouping
Indicates that entities are associated or organized together in an initial or preliminary grouping before a final or primary grouping is established.
-
B.
preGroupingStatus
Indicates the status or condition of an entity before it is grouped or assigned to a group.
-
C.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
D.
preIntegration
Indicates a relationship or state that exists or actions that occur before an integration process takes place.
-
E.
prePartitionCommunity
Indicates a relationship where entities belong to or are associated with the same community as it existed before a specific partition or division event.
- F. None of above. chosen
Provenance (4 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6e0814081908a81e1ede05ab810 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:52 p.m.