Triple
T17102574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lünen |
E415014
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | St. Marien Church |
E337296
|
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: St. Marien Church | Statement: [Lünen, hasLandmark, St. Marien Church]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: St. Marien Church Context triple: [Lünen, hasLandmark, St. Marien Church]
-
A.
St. Marien Church
chosen
St. Marien Church is a historic Christian church and notable architectural landmark located in the town of Lünen, Germany.
-
B.
St. Marien Church
St. Marien Church is a historic Lutheran church and prominent architectural landmark in the city of Flensburg, Germany.
-
C.
St. Marien Church
St. Marien Church is a historic Christian church in Freyburg (Unstrut), Germany, noted for its medieval architecture and cultural significance in the region.
-
D.
St. Marien Church
St. Marien Church is a historic Christian church in Lemgo, Germany, noted for its medieval architecture and cultural significance in the region.
-
E.
St. Marien church
St. Marien church is a historic Christian church and notable architectural landmark located in Roßlau (Elbe), Germany.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2495c88190b5b16a006a994faf |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139ffbe808190a24e827331ee4a6c |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:35 a.m.