Triple
T24285030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolniki District |
E605645
|
entity |
| Predicate | hasParkActivity |
P19746
|
FINISHED |
| Object | seasonal fairs in Sokolniki Park |
—
|
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: seasonal fairs in Sokolniki Park | Statement: [Sokolniki District, hasParkActivity, seasonal fairs in Sokolniki Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkActivity Context triple: [Sokolniki District, hasParkActivity, seasonal fairs in Sokolniki Park]
-
A.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
B.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park area.
-
C.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasParkSection
Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
-
E.
hasParks
Indicates that one entity possesses, contains, or is associated with one or more parks.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f54c5948190a28207d47d6205e4 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.