Triple
T29887284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haarlem–Leiden corridor |
E759049
|
entity |
| Predicate | urbanCentersServed |
P163466
|
FINISHED |
| Object | Haarlem urban area |
—
|
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: Haarlem urban area | Statement: [Haarlem–Leiden corridor, urbanCentersServed, Haarlem urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCentersServed Context triple: [Haarlem–Leiden corridor, urbanCentersServed, Haarlem urban area]
-
A.
urbanCenterServed
chosen
Indicates that a particular urban center is provided with services or coverage by a specified entity (such as an infrastructure system, facility, or organization).
-
B.
majorEmploymentCentersServed
Indicates that the subject provides access or service to significant hubs of employment, such as large workplaces or business districts.
-
C.
urbanCentersCount
Indicates the number of urban centers associated with or contained within a given entity.
-
D.
primaryCitiesServed
Indicates the main cities that are directly served or covered by a given entity’s services or operations.
-
E.
modernCityServed
Indicates that a modern city receives services, support, or functions (such as transportation, utilities, or administration) from a specified provider or infrastructure.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 6 p.m.