Triple
T37098461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crewe–Birmingham railway line |
E918629
|
entity |
| Predicate | linksJunction |
P187140
|
FINISHED |
| Object | Crewe railway junction |
—
|
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: Crewe railway junction | Statement: [Crewe–Birmingham railway line, linksJunction, Crewe railway junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksJunction Context triple: [Crewe–Birmingham railway line, linksJunction, Crewe railway junction]
-
A.
linkedSite
Indicates that one site has an explicit hyperlink or reference connection to another site.
-
B.
linkedRight
Indicates that one entity is directly connected or positioned to the right of another entity in a sequence or structure.
-
C.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
D.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
E.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.