Triple
T591177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austro-Bavarian German |
E17273
|
entity |
| Predicate | writingStandard |
P8779
|
FINISHED |
| Object | Standard German orthography |
—
|
LITERAL 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: Standard German orthography | Statement: [Austro-Bavarian German, writingStandard, Standard German orthography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingStandard Context triple: [Austro-Bavarian German, writingStandard, Standard German orthography]
-
A.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
-
B.
writingTool
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
-
C.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
editorialStandard
chosen
Indicates that one entity defines, follows, or enforces a particular set of editorial rules, guidelines, or quality criteria in relation to another entity or content.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.