Triple
T28950076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich campus |
E730984
|
entity |
| Predicate | locatedInBusinessHub |
P40
|
FINISHED |
| Object | Munich metropolitan region |
—
|
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: Munich metropolitan region | Statement: [Munich campus, locatedInBusinessHub, Munich metropolitan region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBusinessHub Context triple: [Munich campus, locatedInBusinessHub, Munich metropolitan region]
-
A.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
B.
hasBusinessCenter
Indicates that an entity includes, contains, or is equipped with a business center facility.
-
C.
Global HubLocation
Indicates a location that serves as a central, primary hub for global operations, connections, or activities.
-
D.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
locatedInEducationalHub
Indicates that an entity is situated within a place recognized as a center or hub of educational activity or institutions.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: April 28, 2026, 8:43 a.m.