Triple

T22878071
Position Surface form Disambiguated ID Type / Status
Subject Munkegata E567380 entity
Predicate hasNameMeaning P1966 FINISHED
Object Monks Street
Monks Street is the English meaning of the Norwegian street name "Munkegata," typically referring to a historic thoroughfare associated with monastic or ecclesiastical heritage.
 E2000597 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: Monks Street | Statement: [Munkegata, hasNameMeaning, Monks Street]
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: Monks Street
Triple: [Munkegata, hasNameMeaning, Monks Street]
Generated description
Monks Street is the English meaning of the Norwegian street name "Munkegata," typically referring to a historic thoroughfare associated with monastic or ecclesiastical heritage.

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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f5a26f4819086ede6d85a2ab2bf completed April 29, 2026, 3:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2f46a8dcf88190b7332a3292fcd458 completed June 15, 2026, 12:26 a.m.
NEDg Description generation batch_6a2f47826e888190bf53625d64da61a8 completed June 15, 2026, 12:29 a.m.
NED2 Entity disambiguation (via description) batch_6a301ae519348190a8563be3d2c124d0 completed June 15, 2026, 3:31 p.m.
Created at: April 17, 2026, 3:39 p.m.