Triple
T38164237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German spelling reform of 1996 |
E953100
|
entity |
| Predicate | transitionPeriodUntil |
P164034
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [German spelling reform of 1996, transitionPeriodUntil, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionPeriodUntil Context triple: [German spelling reform of 1996, transitionPeriodUntil, 2004]
-
A.
transitionPeriodContext
Indicates the contextual circumstances or conditions under which a transition period between states, phases, or regimes takes place.
-
B.
establishedTransitionPeriod
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
-
C.
transferPeriod
Indicates the time span or interval during which a transfer from one entity to another takes place.
-
D.
transitionDate
Indicates the date on which a change from one state, status, or condition to another takes place.
-
E.
endingPeriod
chosen
Indicates that a specified time span or process concludes at the given period or point in time.
- 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_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:21 p.m.