Triple
T34498715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salzburgen im Elsaß |
E885688
|
entity |
| Predicate | writtenWithDiacritics |
P2270
|
FINISHED |
| Object | Salzburgen im Elsaß |
—
|
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: Salzburgen im Elsaß | Statement: [Salzburgen im Elsaß, writtenWithDiacritics, Salzburgen im Elsaß]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenWithDiacritics Context triple: [Salzburgen im Elsaß, writtenWithDiacritics, Salzburgen im Elsaß]
-
A.
usesDiacritics
chosen
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
B.
usesDiacriticsFrom
Indicates that one entity employs or incorporates the diacritical marks that originate from or are characteristic of another entity.
-
C.
writtenWithCharacter
Indicates that something is written using a particular character or set of characters as its writing system or notation.
-
D.
isWrittenWith
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
E.
diacriticFunction
Indicates that a diacritic serves a particular role or effect in relation to the base character or linguistic unit it modifies.
- F. None of above.
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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.