Triple
T34015632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumünster–Flensburg railway |
E872233
|
entity |
| Predicate | servesInlandCity |
P200209
|
FINISHED |
| Object | Neumünster |
—
|
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: Neumünster | Statement: [Neumünster–Flensburg railway, servesInlandCity, Neumünster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesInlandCity Context triple: [Neumünster–Flensburg railway, servesInlandCity, Neumünster]
-
A.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
-
B.
isInlandCity
Indicates that a city is located away from the coast, without direct access to the sea or ocean.
-
C.
isInlandTown
Indicates that a town is located away from the coast, without direct access to the sea or ocean.
-
D.
servesCityIndirectly
Indicates that an entity provides services or benefits to a city in an indirect or intermediary manner, rather than through direct interaction.
-
E.
connectsInlandCityToCoast
Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
- F. None of above. chosen
Provenance (4 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: May 1, 2026, 1:51 a.m.