Triple
T20771973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-Bahn Hamburg GmbH |
E511257
|
entity |
| Predicate | hasMainCustomerBase |
P33576
|
FINISHED |
| Object | commuters in Hamburg metropolitan 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: commuters in Hamburg metropolitan area | Statement: [S-Bahn Hamburg GmbH, hasMainCustomerBase, commuters in Hamburg metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCustomerBase Context triple: [S-Bahn Hamburg GmbH, hasMainCustomerBase, commuters in Hamburg metropolitan area]
-
A.
hasCustomers
chosen
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
B.
hasMainSite
Indicates that one entity is designated as the primary or central site associated with another entity.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
hasNotableConsumerBase
Indicates that an entity is recognized for having a significant or prominent group of consumers or users.
-
E.
hasMainHubThroughSubsidiary
Indicates that an entity’s primary hub or central location is established or operated indirectly through one or more of its subsidiary entities.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2681ff88190bfe5938c2db6b2c4 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.