Triple
T22720387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großhadern |
E561842
|
entity |
| Predicate | locatedInDirectionFromCenterOfMunich |
P26962
|
FINISHED |
| Object | southwest |
—
|
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: southwest | Statement: [Großhadern, locatedInDirectionFromCenterOfMunich, southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromCenterOfMunich Context triple: [Großhadern, locatedInDirectionFromCenterOfMunich, southwest]
-
A.
distanceToMunich
Indicates the spatial distance between a given entity’s location and the city of Munich.
-
B.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
C.
directionFromCityCentre
chosen
Indicates the compass direction in which one location lies relative to the city centre.
-
D.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
E.
MunichAirDisasterLocation
Indicates the location where the Munich air disaster took place.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17910deb48190b38174e16868f3dd |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:19 p.m.