Triple
T11533004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ulica Rakowicka |
E273468
|
entity |
| Predicate | isAccessRoadTo |
P9041
|
FINISHED |
| Object | Rakowicki Cemetery main entrance |
—
|
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: Rakowicki Cemetery main entrance | Statement: [ulica Rakowicka, isAccessRoadTo, Rakowicki Cemetery main entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessRoadTo Context triple: [ulica Rakowicka, isAccessRoadTo, Rakowicki Cemetery main entrance]
-
A.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
B.
isPublicRoad
Indicates that a given road is officially designated and accessible for use by the general public.
-
C.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
D.
isMainRoad
Indicates that a road serves as a primary or major thoroughfare within a transportation network.
-
E.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839a2c7081909c285d1f6beb971c |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.