Triple
T31328535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nocera Umbra railway station |
E798960
|
entity |
| Predicate | railwayNetworkScope |
P5684
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Nocera Umbra railway station, railwayNetworkScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayNetworkScope Context triple: [Nocera Umbra railway station, railwayNetworkScope, regional]
-
A.
appliesToRailwayNetwork
Indicates that something is relevant or specifically applicable to a railway network as a whole.
-
B.
railroadNetwork
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
-
C.
railroadServiceScope
chosen
Indicates the extent or coverage area within which a railroad service operates or is applicable.
-
D.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
E.
railwayCompanyNetwork
Indicates a relationship where a railway company operates, manages, or is responsible for a particular rail network or system.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 9:16 p.m.