Triple
T7831692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiel Center |
E181583
|
entity |
| Predicate | renamingToSavvisCenterYear |
P1742
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Kiel Center, renamingToSavvisCenterYear, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamingToSavvisCenterYear Context triple: [Kiel Center, renamingToSavvisCenterYear, 2000]
-
A.
renamedYear
chosen
Indicates the year in which an entity underwent a renaming or change of name.
-
B.
serviceRenamedAs
Indicates that a service previously known by one name is now identified or referred to by a different name.
-
C.
redesignationYear
Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
-
D.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
E.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb0647848081908d74e09f52d0919e |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.