Triple
T6979803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue du Luxembourg |
E161811
|
entity |
| Predicate | hasNameInDutch |
P13254
|
FINISHED |
| Object |
Luxemburgstraat
Luxemburgstraat is the Dutch name for Rue du Luxembourg, a street in Brussels, Belgium.
|
E634251
|
NE FINISHED |
How this triple was built (4 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: Luxemburgstraat | Statement: [Rue du Luxembourg, hasNameInDutch, Luxemburgstraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luxemburgstraat Context triple: [Rue du Luxembourg, hasNameInDutch, Luxemburgstraat]
-
A.
Valkenburgerstraat
Valkenburgerstraat is a street in central Amsterdam, Netherlands, located near the Waterlooplein area and served by the city’s metro network.
-
B.
Koningsstraat
Koningsstraat is a major central street in Brussels, Belgium, known for its straight, ceremonial layout and its role connecting key royal and administrative landmarks.
-
C.
Rozenstraat
Rozenstraat is a street in Amsterdam’s historic Jordaan neighborhood, known for its traditional canal-side architecture and local character.
-
D.
Servetstraat
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
-
E.
Utrechtsestraat
Utrechtsestraat is a well-known shopping and dining street in central Amsterdam, noted for its historic canalside setting and mix of boutiques, cafés, and restaurants.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Luxemburgstraat Triple: [Rue du Luxembourg, hasNameInDutch, Luxemburgstraat]
Generated description
Luxemburgstraat is the Dutch name for Rue du Luxembourg, a street in Brussels, Belgium.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Luxemburgstraat Target entity description: Luxemburgstraat is the Dutch name for Rue du Luxembourg, a street in Brussels, Belgium.
-
A.
Valkenburgerstraat
Valkenburgerstraat is a street in central Amsterdam, Netherlands, located near the Waterlooplein area and served by the city’s metro network.
-
B.
Koningsstraat
Koningsstraat is a major central street in Brussels, Belgium, known for its straight, ceremonial layout and its role connecting key royal and administrative landmarks.
-
C.
Rozenstraat
Rozenstraat is a street in Amsterdam’s historic Jordaan neighborhood, known for its traditional canal-side architecture and local character.
-
D.
Servetstraat
Servetstraat is a small historic street located near Dom Square in the center of Utrecht, Netherlands.
-
E.
Utrechtsestraat
Utrechtsestraat is a well-known shopping and dining street in central Amsterdam, noted for its historic canalside setting and mix of boutiques, cafés, and restaurants.
- F. None of above. chosen
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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6c1efc8190ab1575ae2ce726db |
completed | March 27, 2026, 7:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c76a0e34288190ad2decbc18190c6b |
completed | March 28, 2026, 5:41 a.m. |
| NEDg | Description generation | batch_69c76b2c3ca481909df85ef915a91f10 |
completed | March 28, 2026, 5:46 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c76ba3f8ec8190af87316fc63b523e |
completed | March 28, 2026, 5:48 a.m. |
Created at: March 27, 2026, 2:31 p.m.