Triple

T33403666
Position Surface form Disambiguated ID Type / Status
Subject Stockholm Municipality E855380 entity
Predicate hasSubdivision P747 FINISHED
Object Rinkeby-Kista
Rinkeby-Kista is a borough in western Stockholm known for its diverse population and the major business and technology hub centered around Kista Science City.
E2053818 NE 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: Rinkeby-Kista | Statement: [Stockholm Municipality, hasSubdivision, Rinkeby-Kista]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Rinkeby-Kista
Triple: [Stockholm Municipality, hasSubdivision, Rinkeby-Kista]
Generated description
Rinkeby-Kista is a borough in western Stockholm known for its diverse population and the major business and technology hub centered around Kista Science City.

Provenance (5 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_69f3496e3f1c8190bcecfa82aa9d17ff completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e41934c48190a60feb21405199c5 completed May 3, 2026, 5:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a35959a6f708190b6dfa8607062dcfc completed June 19, 2026, 7:16 p.m.
NEDg Description generation batch_6a359645042c8190829495f37496c010 completed June 19, 2026, 7:19 p.m.
NED2 Entity disambiguation (via description) batch_6a3596b879a08190b1b4a633c7fb2745 completed June 19, 2026, 7:21 p.m.
Created at: May 1, 2026, 1:36 a.m.