Triple
T4581693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aarhus |
E101867
|
entity |
| Predicate | spellingChangeYear |
P45284
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Aarhus, spellingChangeYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spellingChangeYear Context triple: [Aarhus, spellingChangeYear, 2011]
-
A.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
B.
spellingStability
Indicates the degree to which the spelling of a word or term remains consistent over time or across different uses.
-
C.
replacedInYear
Indicates that one entity took the place of or superseded another entity in a specific calendar year.
-
D.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
-
E.
languageReform
chosen
Indicates efforts or actions aimed at changing, standardizing, or improving aspects of a language, such as its spelling, grammar, or usage rules.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd590116e88190b8495b2a78cf3fb6 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.