Triple
T36332319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamburg Airport station |
E894682
|
entity |
| Predicate | distanceToCityCentreByRail |
P65643
|
FINISHED |
| Object | approximately 25 minutes |
—
|
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: approximately 25 minutes | Statement: [Hamburg Airport station, distanceToCityCentreByRail, approximately 25 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCityCentreByRail Context triple: [Hamburg Airport station, distanceToCityCentreByRail, approximately 25 minutes]
-
A.
distanceToByRail
chosen
Indicates the distance between two locations when traveling via railway routes.
-
B.
distanceToRailhead
Indicates the measured distance between a location or object and the nearest railhead (rail transport access point).
-
C.
distanceFromStation
Indicates the measured spatial separation between an entity and a specified station.
-
D.
roadDistanceToCityCentre_km
Indicates the distance in kilometers from a location to the city centre when traveling by road.
-
E.
hasNearbyRailwayStation
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
- 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.