Triple
T22681791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trg republike |
E560499
|
entity |
| Predicate | pedestrianizationCompletedIn |
P106161
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Trg republike, pedestrianizationCompletedIn, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianizationCompletedIn Context triple: [Trg republike, pedestrianizationCompletedIn, 2019]
-
A.
pedestrianizationCompleted
chosen
Indicates that the process of converting an area for exclusive or primary use by pedestrians has been fully completed.
-
B.
pedestrianizedSince
Indicates that an area or street has been designated for pedestrian use only starting from a specific point in time.
-
C.
pedestrianizedDuring
Indicates that a location or route is designated for pedestrian-only use during a specified time period or interval.
-
D.
hasPedestrianisationProjects
Indicates that an entity is involved in or associated with projects aimed at restricting or redesigning areas for pedestrian use.
-
E.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786113a881908f60285054d7ecfb |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.