Triple
T20689087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian railway line 57 |
E508500
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Schoonaarde |
—
|
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: Schoonaarde | Statement: [Belgian railway line 57, connects, Schoonaarde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schoonaarde Context triple: [Belgian railway line 57, connects, Schoonaarde]
-
A.
Schoonaarde
chosen
Schoonaarde is a village in East Flanders, Belgium, that forms a sub-municipality of the city of Dendermonde.
-
B.
Schoondijke
Schoondijke is a village in the Dutch province of Zeeland, known for its rural character and location near the North Sea coast.
-
C.
Schoonrewoerd
Schoonrewoerd is a small village in the Dutch province of Utrecht, known for its rural character and historic church.
-
D.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
-
E.
Vriezekoop
Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10b7b808190bdb8b08e53168fb8 |
completed | April 21, 2026, 12:12 a.m. |
Created at: April 16, 2026, 11:56 a.m.