Triple
T6942820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemkade |
E160718
|
entity |
| Predicate | hasVenue |
P373
|
FINISHED |
| Object | Hemkade 48 |
E160718
|
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: Hemkade 48 | Statement: [Hemkade, hasVenue, Hemkade 48]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hemkade 48 Context triple: [Hemkade, hasVenue, Hemkade 48]
-
A.
Hemkade
chosen
Hemkade is a waterfront area near Amsterdam known for its industrial setting and event venues, accessible via the city's ferry network.
-
B.
Hem
Hem is a suburban commune in northern France located near the city of Lille.
-
C.
Hemiksem
Hemiksem is a municipality in the Belgian province of Antwerp, situated along the Rupel River and known for its historical abbey and industrial heritage.
-
D.
Nahan
Nahan is a small hill town and municipal council in Himachal Pradesh, India, known for its scenic surroundings, pleasant climate, and role as a regional administrative and commercial center.
-
E.
Kadayan
Kadayan is an alternative name for the Kedayan language, an Austronesian language spoken primarily in Brunei, Sabah, and parts of Sarawak.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da876c9c8190996f3ff84858e8d1 |
completed | March 27, 2026, 7:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7515bb4688190a81bef732676eb4e |
completed | March 28, 2026, 3:56 a.m. |
Created at: March 27, 2026, 2:28 p.m.