Triple
T19313883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angria |
E483042
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Engern |
—
|
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: Engern | Statement: [Angria, hasAlternativeName, Engern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Engern Context triple: [Angria, hasAlternativeName, Engern]
-
A.
Engern
chosen
Engern is the German name for Angria, a historical region in what is now northwestern Germany.
-
B.
Ehrwald
Ehrwald is a picturesque Austrian village in Tyrol, known as a popular alpine resort and gateway to the Zugspitze massif.
-
C.
Engen
Engen is a surname of Norwegian origin borne by various notable individuals across fields such as aviation, sports, and public service.
-
D.
Eggerberg
Eggerberg is a small Swiss municipality in the canton of Valais, known for its hillside location above the Rhône valley and views of the surrounding Alps.
-
E.
Enniger
Enniger is a village and district within the town of Ennigerloh in North Rhine-Westphalia, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cfec8c8190a118b327b1418150 |
completed | April 20, 2026, 10:49 a.m. |
Created at: April 10, 2026, 1:32 p.m.