Triple
T26327713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wylam Colliery railway |
E662299
|
entity |
| Predicate | railProfile |
P160250
|
FINISHED |
| Object | L-shaped plate rails |
—
|
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: L-shaped plate rails | Statement: [Wylam Colliery railway, railProfile, L-shaped plate rails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railProfile Context triple: [Wylam Colliery railway, railProfile, L-shaped plate rails]
-
A.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
-
B.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
C.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
D.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
E.
railcodeSystem
Indicates a relationship where a rail-specific code is assigned to, used by, or governs a particular system within a railway context.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f65f9f48190ba299fb3e435e67a |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:32 p.m.