Triple
T6887411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grave |
E158956
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Hampoort (city gate) |
E20679
|
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: Hampoort (city gate) | Statement: [Grave, hasLandmark, Hampoort (city gate)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hampoort (city gate) Context triple: [Grave, hasLandmark, Hampoort (city gate)]
-
A.
Hampoort city gate
chosen
Hampoort city gate is a historic town gate in Grave, Netherlands, notable as a remnant of the city’s former fortifications.
-
B.
Koepoort city gate
Koepoort city gate is a historic fortified entrance of the Dutch city of Middelburg, notable for its architectural and cultural heritage.
-
C.
Burgtor
Burgtor is a historic city gate in Lübeck, Germany, notable as part of the city’s medieval fortifications and Hanseatic architectural heritage.
-
D.
Bolwerk city ramparts
The Bolwerk city ramparts are the historic defensive earthworks and fortifications surrounding the Frisian town of Franeker in the Netherlands.
-
E.
Erer Gate
Erer Gate is one of the historic gateways in the ancient walled city of Harar Jugol in eastern Ethiopia.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d90e92488190b738676342ac6393 |
completed | March 27, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742e249508190ac95be97c0409d4a |
completed | March 28, 2026, 2:54 a.m. |
Created at: March 27, 2026, 2:23 p.m.