Triple
T20603044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian railway line 52 |
E506230
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Schellebelle |
—
|
NE NERFINISHED |
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: Schellebelle | Statement: [Belgian railway line 52, connects, Schellebelle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schellebelle Context triple: [Belgian railway line 52, connects, Schellebelle]
-
A.
Schellebelle
chosen
Schellebelle is a village in East Flanders, Belgium, known for its railway station and location along the Scheldt River.
-
B.
Schelle
Schelle is a municipality in the Belgian province of Antwerp, situated along the Rupel River.
-
C.
Gerbelle
Gerbelle is a small settlement located within the alpine commune of Valgrisenche in Italy’s Aosta Valley region.
-
D.
Shantallow
Shantallow is a residential area and electoral ward in the city of Derry, Northern Ireland.
-
E.
Melfina
Melfina is a mysterious bio-android and key crew member of the spaceship Outlaw Star in the anime series of the same name.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa22663881909a8d4644e1c48dc2 |
completed | April 20, 2026, 10:35 p.m. |
Created at: April 16, 2026, 11:41 a.m.