Triple
T38164225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German spelling reform of 1996 |
E953100
|
entity |
| Predicate | introducedChangeIn |
P100259
|
FINISHED |
| Object | use of ß and ss |
—
|
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: use of ß and ss | Statement: [German spelling reform of 1996, introducedChangeIn, use of ß and ss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedChangeIn Context triple: [German spelling reform of 1996, introducedChangeIn, use of ß and ss]
-
A.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
-
D.
updateIntroduced
chosen
Indicates that a change or modification was newly added or introduced to an existing entity or system.
-
E.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:21 p.m.