Triple
T21414877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drem railway station |
E528272
|
entity |
| Predicate | hasJunctionRole |
P61974
|
FINISHED |
| Object | former junction for lines to Luffness |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: former junction for lines to Luffness | Statement: [Drem railway station, hasJunctionRole, former junction for lines to Luffness]
Provenance (2 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d16bfc8190a1c08dd9d0c80e02 |
completed | April 26, 2026, 7:09 p.m. |
Created at: April 16, 2026, 5:45 p.m.