Triple
T9259447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lier |
E222534
|
entity |
| Predicate | connectedByRailTo |
P848
|
FINISHED |
| Object | Aarschot |
E653742
|
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: Aarschot | Statement: [Lier, connectedByRailTo, Aarschot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aarschot Context triple: [Lier, connectedByRailTo, Aarschot]
-
A.
Aarschot
chosen
Aarschot is a historic city in Belgium known for its medieval architecture, including a prominent Gothic church, and its location along the Demer River.
-
B.
Hasselt
Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
-
C.
Hasselt
Hasselt is a city in northeastern Belgium that serves as the capital of the province of Limburg in the Flemish region.
-
D.
Vilvoorde
Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan area.
-
E.
Edegem
Edegem is a municipality in the Belgian province of Antwerp, known as a residential suburb south of the city of Antwerp.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0714317481908405f857a4f49e74 |
completed | April 1, 2026, 11:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc2ca7a081908f597e9a58920d6e |
completed | April 5, 2026, 2:42 a.m. |
Created at: March 30, 2026, 7:32 p.m.