Triple
T6609869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels South Charleroi Airport |
E149208
|
entity |
| Predicate | distanceFromBrussels |
P26827
|
FINISHED |
| Object | about 46 km south of 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: about 46 km south of Brussels | Statement: [Brussels South Charleroi Airport, distanceFromBrussels, about 46 km south of Brussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBrussels Context triple: [Brussels South Charleroi Airport, distanceFromBrussels, about 46 km south of Brussels]
-
A.
cityDistanceFromBrussels_km
chosen
Indicates the distance, measured in kilometers, between a given city and Brussels.
-
B.
distanceToBredaKmApproximate
Indicates an approximate distance, measured in kilometers, from an entity to the location Breda.
-
C.
cityDistanceFromBrussels_miles
Indicates the physical distance, measured in miles, between a given city and Brussels.
-
D.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
-
E.
distanceToBasel_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Basel.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.