Triple
T35715574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hdb |
E1031993
|
entity |
| Predicate | locationStationName |
—
|
GENERATED |
| Object | Heemstede-Aerdenhout |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationStationName Context triple: [Hdb, locationStationName, Heemstede-Aerdenhout]
-
A.
nearbyStationName
Indicates that the predicate specifies the name of a station that is geographically close to a given reference point or entity.
-
B.
stationName
chosen
Indicates the name assigned to a particular station in the relationship.
-
C.
ownedStation
Indicates that one entity possesses ownership or control over a particular station.
-
D.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
E.
stationNumber
Indicates the specific station identifier or code assigned to an entity within a system or network.
- F. None of above.
Provenance (1 batch)
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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.