Triple
T16210544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prague 2 |
E393450
|
entity |
| Predicate | hasSignificantGreenAreas |
P45219
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Prague 2, hasSignificantGreenAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantGreenAreas Context triple: [Prague 2, hasSignificantGreenAreas, yes]
-
A.
hasGreenSpaces
chosen
Indicates that an entity includes or is associated with areas of vegetation or natural greenery, such as parks, gardens, or lawns.
-
B.
isGreenSpaceFor
Indicates that one entity serves as a designated green or open space intended for use or benefit by another entity.
-
C.
hasNearbyGreenSpace
Indicates that an entity is located close to an area of green space, such as a park, garden, or natural vegetation.
-
D.
isGreenInfrastructure
Indicates that something functions as green infrastructure, meaning it is a natural or nature-based system designed to provide environmental benefits such as stormwater management, habitat support, or climate regulation.
-
E.
hasVillageGreen
Indicates that one entity possesses or includes a village green as part of its area or facilities.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22713282481909c7c0d0782213461 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.