Triple
T31538382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diegem |
E804672
|
entity |
| Predicate | nearInternationalTransportHub |
P171946
|
FINISHED |
| Object | Brussels Airport |
—
|
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: Brussels Airport | Statement: [Diegem, nearInternationalTransportHub, Brussels Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearInternationalTransportHub Context triple: [Diegem, nearInternationalTransportHub, Brussels Airport]
-
A.
nearestMajorTransportHub
Indicates that one location is the closest significant transportation center (such as a major train station, airport, or bus terminal) to another location.
-
B.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
C.
nearCommuterRailStation
Indicates that one entity is located close to, or within a short walking distance of, a commuter rail station.
-
D.
nearestPassengerRailStation
Indicates that one entity is the closest passenger rail station in distance to another entity.
-
E.
nearbyHeritageStation
Indicates that one entity is located close to a heritage (historically or culturally significant) station.
- F. None of above. chosen
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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:05 p.m.