Triple
T33730870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTRX |
E864269
|
entity |
| Predicate | operatesHighSpeedServicesOn |
P48478
|
FINISHED |
| Object | Stockholm–Gothenburg route |
—
|
NE NERFINISHED |
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: Stockholm–Gothenburg route | Statement: [MTRX, operatesHighSpeedServicesOn, Stockholm–Gothenburg route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesHighSpeedServicesOn Context triple: [MTRX, operatesHighSpeedServicesOn, Stockholm–Gothenburg route]
-
A.
hasHighSpeedLine
chosen
Indicates that there exists a high-speed rail line connection between the related entities.
-
B.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
-
C.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
D.
railwayTypeServed
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.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
Created at: May 1, 2026, 1:44 a.m.