Triple
T32796519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrovskaya Ploshchad |
E838779
|
entity |
| Predicate | usedAsGatheringPlace |
P16368
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Petrovskaya Ploshchad, usedAsGatheringPlace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsGatheringPlace Context triple: [Petrovskaya Ploshchad, usedAsGatheringPlace, true]
-
A.
gatheringPlace
chosen
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
B.
traditionalMeetingPlace
Indicates that a location is customarily used as a gathering spot for meetings or social interactions according to established tradition.
-
C.
usedInTown
Indicates that something is utilized, applied, or functions within the context or boundaries of a particular town.
-
D.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
E.
usualVenueSince
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 1, 2026, 1:14 a.m.