Triple
T29305646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berchem district |
E743085
|
entity |
| Predicate | railJunctionRole |
P14468
|
FINISHED |
| Object | major junction for trains to Brussels |
—
|
LITERAL 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: major junction for trains to Brussels | Statement: [Berchem district, railJunctionRole, major junction for trains to Brussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railJunctionRole Context triple: [Berchem district, railJunctionRole, major junction for trains to Brussels]
-
A.
railwayLineRole
Indicates the specific functional role or purpose that a railway line serves within a rail network or transportation system.
-
B.
railwayTrafficRole
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
-
C.
railNetworkRole
Indicates the specific function or responsibility an entity has within a rail network system.
-
D.
railwayJunctionFor
chosen
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
-
E.
railInterface
Indicates a connection or interaction between entities via a rail-based system or interface.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a631948190bb1a8cbb5df633ae |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:13 p.m.