Triple
T32764715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin railway network |
E837858
|
entity |
| Predicate | coreCityServed |
P144103
|
FINISHED |
| Object | Berlin |
—
|
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: Berlin | Statement: [Berlin railway network, coreCityServed, Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreCityServed Context triple: [Berlin railway network, coreCityServed, Berlin]
-
A.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
-
B.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
-
C.
primaryCitiesServed
chosen
Indicates the main cities that are directly served or covered by a given entity’s services or operations.
-
D.
modernCityServed
Indicates that a modern city receives services, support, or functions (such as transportation, utilities, or administration) from a specified provider or infrastructure.
-
E.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.