Triple
T13407357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blayney railway station |
E319994
|
entity |
| Predicate | hasSignalType |
P4618
|
FINISHED |
| Object | mechanical 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: mechanical signalling | Statement: [Blayney railway station, hasSignalType, mechanical signalling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignalType Context triple: [Blayney railway station, hasSignalType, mechanical signalling]
-
A.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
hasSignTypes
Indicates that an entity is associated with one or more specific types or categories of signs.
-
C.
transportsSignalType
Indicates that one entity carries or conveys a particular type of signal from one point to another.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasSignalLine
Indicates that one entity is connected to another by a signal-carrying line or path used for transmitting information or control signals.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4be498819094798473a1bfd853 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.