Triple
T633339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Aerospace Center |
E15966
|
entity |
| Predicate | hasResearchCenterIn |
P11730
|
FINISHED |
| Object | Weßling |
E66087
|
NE 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: Weßling | Statement: [German Aerospace Center, hasResearchCenterIn, Weßling]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weßling Context triple: [German Aerospace Center, hasResearchCenterIn, Weßling]
-
A.
Würschnitz
Würschnitz is a small river in Saxony, Germany, that serves as one of the tributaries feeding into the Chemnitz River.
-
B.
Brigach
Brigach is a river in Germany that forms one of the two headstreams of the Danube.
-
C.
Zwönitz
Zwönitz is a river in Saxony, Germany, that serves as one of the headstreams of the Chemnitz River.
-
D.
Lommersweiler
Lommersweiler is a village and municipal section of the town of St. Vith in the German-speaking Community of eastern Belgium.
-
E.
Pöcking
chosen
Pöcking is a municipality in Bavaria, Germany, located on the western shore of Lake Starnberg and known for its affluent residential character.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a515ceb081908c064b2082047c0f |
completed | March 1, 2026, 8:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a64a4ba2d88190969e7c777a1bbfd7 |
completed | March 3, 2026, 2:41 a.m. |
Created at: March 1, 2026, 7:35 p.m.