Triple
T36995073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht rail node |
E915207
|
entity |
| Predicate | connectsTypeOfService |
P149668
|
FINISHED |
| Object | intercity 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: intercity trains | Statement: [Utrecht rail node, connectsTypeOfService, intercity trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTypeOfService Context triple: [Utrecht rail node, connectsTypeOfService, intercity trains]
-
A.
connectsServiceType
chosen
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
-
B.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
C.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
D.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
E.
connectsTypeOfHub
Indicates that one entity is linked to another entity that functions as a specific type of hub within a 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 3, 2026, 4:14 p.m.