Triple
T3933028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leiden Lammenschans |
E90838
|
entity |
| Predicate | hasNearbyTransportMode |
P31014
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [Leiden Lammenschans, hasNearbyTransportMode, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTransportMode Context triple: [Leiden Lammenschans, hasNearbyTransportMode, bus]
-
A.
hasPublicTransitMode
chosen
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
-
B.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
C.
hasNearbyTramStop
Indicates that a location has a tram stop situated within a short walking distance or close proximity.
-
D.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
E.
hasPublicTransportStop
Indicates that a location or area contains or is served by a public transport stop, such as a bus, tram, or train stop.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcab1808190bf653f29062cdddb |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.