Triple
T4907827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mže |
E109954
|
entity |
| Predicate | GermanName |
P6492
|
FINISHED |
| Object | Mies |
E171317
|
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: Mies | Statement: [Mže, GermanName, Mies]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mies Context triple: [Mže, GermanName, Mies]
-
A.
Mies
chosen
Mies is a small Swiss municipality in the canton of Vaud, located along Lake Geneva near the city of Geneva.
-
B.
Mann
Mann is a common German surname borne by numerous notable figures in literature, politics, and the arts.
-
C.
Man
Man was a prominent British anthropological journal that served as the main publication of the Royal Anthropological Institute before being continued under a new title.
-
D.
MAN
MAN is the three-letter IATA airport code for Manchester Airport, a major international airport serving the Greater Manchester area in England.
-
E.
MAN
MAN is a German commercial vehicle and engineering company best known for manufacturing trucks, buses, and diesel engines.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e7452d481909078a0027e2a4566 |
completed | March 20, 2026, 3:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fe098b081908e17d6d349b76364 |
completed | March 21, 2026, 10:16 a.m. |
Created at: March 20, 2026, 1:29 p.m.