Triple
T26139663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels–Tournai railway line |
E659480
|
entity |
| Predicate | formsCorridorTowards |
P80212
|
FINISHED |
| Object | western Belgium |
—
|
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: western Belgium | Statement: [Brussels–Tournai railway line, formsCorridorTowards, western Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsCorridorTowards Context triple: [Brussels–Tournai railway line, formsCorridorTowards, western Belgium]
-
A.
focusesOnCorridor
Indicates that an action, attention, or process is directed specifically toward a corridor or passageway.
-
B.
corridorFunction
chosen
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
-
C.
followedCorridor
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
D.
parallelCorridorFor
Indicates that one corridor runs alongside and in the same general direction as another corridor, forming a parallel passage.
-
E.
corridorOrientation
Indicates the directional alignment or bearing of a corridor relative to a reference frame or coordinate system.
- F. None of above.
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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 8:19 p.m.