Triple
T34003762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburger Verkehrsverbund |
E871899
|
entity |
| Predicate | operatesInMode |
P1533
|
FINISHED |
| Object | bus transport |
—
|
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: bus transport | Statement: [Hamburger Verkehrsverbund, operatesInMode, bus transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInMode Context triple: [Hamburger Verkehrsverbund, operatesInMode, bus transport]
-
A.
availableInMode
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
B.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
C.
servesMode
chosen
Indicates that one entity provides or operates in a particular manner, method, or mode in relation to another entity or context.
-
D.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
E.
deploymentModeOfSystem
Indicates the specific deployment configuration or operational mode in which a system is set up or run.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 1, 2026, 1:50 a.m.