Triple
T22530444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahnhof Georgensgmünd |
E557019
|
entity |
| Predicate | servesRailTraffic |
P55099
|
FINISHED |
| Object | regional trains |
—
|
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 trains | Statement: [Bahnhof Georgensgmünd, servesRailTraffic, regional trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRailTraffic Context triple: [Bahnhof Georgensgmünd, servesRailTraffic, regional trains]
-
A.
servesRailTrafficBetween
Indicates that something (typically a rail line, service, or facility) provides rail transportation connecting two or more locations.
-
B.
servesRailCorridor
Indicates that something (such as a service, facility, or operation) provides service to or operates along a specific rail corridor.
-
C.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
D.
railwayTypeServed
chosen
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
E.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed6734881908abbbee477dfab98 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.