Triple
T7371089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanaal Brussel-Schelde |
E170004
|
entity |
| Predicate | hasLock |
P2431
|
FINISHED |
| Object | lock at Zemst |
E142992
|
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: lock at Zemst | Statement: [Kanaal Brussel-Schelde, hasLock, lock at Zemst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: lock at Zemst Context triple: [Kanaal Brussel-Schelde, hasLock, lock at Zemst]
-
A.
Zemst-Centrum
Zemst-Centrum is the central village and administrative core of the municipality of Zemst in Flemish Brabant, Belgium.
-
B.
Ziegelstein
Ziegelstein is a district in Nuremberg, Germany, known for its residential character and proximity to Nuremberg Airport.
-
C.
Zemtsov
Zemtsov is a Russian surname most notably borne by violist Mikhail Zemtsov.
-
D.
Zemba
Zemba is a Bantu language variety spoken primarily in southwestern Angola and northern Namibia, closely related to and often considered a dialect of Herero.
-
E.
Zemst
chosen
Zemst is a municipality in the Belgian province of Flemish Brabant, located in the Flanders region.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f182df5c81908964fbaa3f8ec790 |
completed | March 27, 2026, 9:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802c711788190806987567dbc9942 |
completed | March 28, 2026, 4:33 p.m. |
Created at: March 27, 2026, 3:07 p.m.