Triple
T25599353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Garden of Sofia |
E641742
|
entity |
| Predicate | isPopularGatheringPlace |
P134081
|
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: [City Garden of Sofia, isPopularGatheringPlace, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularGatheringPlace Context triple: [City Garden of Sofia, isPopularGatheringPlace, yes]
-
A.
gatheringPlace
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
B.
isSocialLandmark
chosen
Indicates that a place functions as a notable social gathering point or reference location within a community or area.
-
C.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
D.
isShoppingDistrict
Indicates that a location functions primarily as a shopping district, characterized by a concentration of retail stores and commercial shopping activity.
-
E.
isEntertainmentDistrict
Indicates that a location functions primarily as an area dedicated to entertainment activities, venues, and nightlife.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a53aa48190b935de0228cb5be3 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:30 p.m.