Triple
T14859442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clausen |
E349449
|
entity |
| Predicate | locatedInOrNearby |
P40
|
FINISHED |
| Object | Pfaffenthal |
E1148222
|
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: Pfaffenthal | Statement: [Clausen, locatedInOrNearby, Pfaffenthal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pfaffenthal Context triple: [Clausen, locatedInOrNearby, Pfaffenthal]
-
A.
Pfaffenthal
chosen
Pfaffenthal is a historic quarter of Luxembourg City situated in the Alzette valley below the old town, known for its picturesque setting and traditional architecture.
-
B.
Gersthofen
Gersthofen is a town in Bavaria, Germany, located just north of Augsburg and known for its industrial presence and role as a regional transport hub.
-
C.
Pfaffstätten
Pfaffstätten is a market town in Lower Austria known for its wine-growing tradition and location within the Baden district near Vienna.
-
D.
Pfaffendorf
Pfaffendorf is a district of the German city of Koblenz, situated on the east bank of the Rhine River.
-
E.
Pfaffenberg
Pfaffenberg is a small locality in the Straubing-Bogen district of Bavaria, 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44598e48190b759a05ed2d9ecaf |
completed | April 14, 2026, 11:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9976bc888190a050c2502d1f8e81 |
completed | May 9, 2026, 8:30 p.m. |
Created at: April 10, 2026, 1:54 a.m.