Triple
T35588004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North–South connection |
E1028411
|
entity |
| Predicate | isBusiestRailwaySectionIn |
P5905
|
FINISHED |
| Object | Belgium |
E364
|
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: Belgium | Statement: [North–South connection, isBusiestRailwaySectionIn, Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusiestRailwaySectionIn Context triple: [North–South connection, isBusiestRailwaySectionIn, Belgium]
-
A.
isBusiestPassengerRailLineIn
chosen
Indicates that a passenger rail line is the one with the highest level of use or traffic within a specified geographic area or system.
-
B.
isBusiestStationIn
Indicates that a station has the highest level of activity (e.g., passenger or traffic volume) within a specified area or system.
-
C.
oneOfBusiestStationsIn
Indicates that a station is among the busiest stations within a specified area or system.
-
D.
railwayLineUsage
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
-
E.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
- F. None of above.
Provenance (4 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a385bd6d85c819095ffa228a811efa9 |
completed | June 21, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.