Triple
T25398367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCL |
E636352
|
entity |
| Predicate | usedInRailwayInformationSystems |
P9621
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SCL, usedInRailwayInformationSystems, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRailwayInformationSystems Context triple: [SCL, usedInRailwayInformationSystems, true]
-
A.
usedInRailwayContext
Indicates that something is applied, referenced, or functions specifically within a railway-related context or setting.
-
B.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
C.
usesRailwaySignallingSystem
Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
-
D.
usedForRailwayTimetables
chosen
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
-
E.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 1:50 p.m.