Triple
T951113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Zuid |
E20522
|
entity |
| Predicate | isKeyHubFor |
P523
|
FINISHED |
| Object | regional connections |
—
|
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: regional connections | Statement: [Amsterdam Zuid, isKeyHubFor, regional connections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyHubFor Context triple: [Amsterdam Zuid, isKeyHubFor, regional connections]
-
A.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
B.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
C.
isRailHubFor
chosen
Indicates that a location functions as a central node or interchange point within a rail network for the referenced area, routes, or services.
-
D.
hasKeyOrganization
Indicates that an entity is associated with or primarily represented by a main or primary organization.
-
E.
hasKeyAgency
Indicates that an entity serves as the primary responsible or controlling agency for another entity, action, or process.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d62e408190855b2883407f6c6b |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.