Triple
T34659560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Avenue, Windhoek |
E890068
|
entity |
| Predicate | wasPreviouslyNamed |
P65
|
FINISHED |
| Object | Kaiserstraße |
—
|
NE NERFINISHED |
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: Kaiserstraße | Statement: [Independence Avenue, Windhoek, wasPreviouslyNamed, Kaiserstraße]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPreviouslyNamed Context triple: [Independence Avenue, Windhoek, wasPreviouslyNamed, Kaiserstraße]
-
A.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
B.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
C.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
D.
heldAtFormerName
Indicates that an event or activity took place at a location when it was known by a previous or former name.
-
E.
involvesFormerlyNamed
Indicates that the relationship or action concerns an entity that previously had a different name than it does now.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722cc6d1c8190b3ecaa6ab88ce2fa |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.