Triple
T7620808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antwerp Central Station |
E172484
|
entity |
| Predicate | servesInternationalTrains |
P11099
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Antwerp Central Station, servesInternationalTrains, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesInternationalTrains Context triple: [Antwerp Central Station, servesInternationalTrains, true]
-
A.
servesLocalTrains
Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
-
B.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
C.
operatesInterCityServices
Indicates that an entity runs or provides transportation services connecting different cities.
-
D.
isNationalRailwaySystemOf
Indicates that one entity functions as the official national railway system serving and operating within the territory of another entity.
-
E.
hasInternationalService
chosen
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.