Triple
T25590180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin–Stettin railway |
E641500
|
entity |
| Predicate | hasEndpointCityFormerName |
P26386
|
FINISHED |
| Object | Stettin |
—
|
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: Stettin | Statement: [Berlin–Stettin railway, hasEndpointCityFormerName, Stettin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointCityFormerName Context triple: [Berlin–Stettin railway, hasEndpointCityFormerName, Stettin]
-
A.
hasAssociatedCityFormerName
Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
-
B.
cityThenKnownAs
Indicates that an entity had a particular city name during a specified earlier time period, before it was renamed or became known by a different name.
-
C.
hasEndpointCity
chosen
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
D.
refersToFormerNameOfComparisonCity
Indicates that the subject entity refers to a previous or former name of the comparison city.
-
E.
cityNowKnownAs
Indicates that a city has changed its name and specifies the new name it is currently known by.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 4:19 p.m.