Triple
T6358686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby–Crewe line |
E143054
|
entity |
| Predicate | signallingType |
P4618
|
FINISHED |
| Object | colour light signalling |
—
|
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: colour light signalling | Statement: [Derby–Crewe line, signallingType, colour light signalling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signallingType Context triple: [Derby–Crewe line, signallingType, colour light signalling]
-
A.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
B.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
D.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
E.
usesSignallingPractice
Indicates that one entity employs or follows a particular signalling practice in its communication or behavior.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f72f8481908f9df0c0cdf22a52 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.