Triple
T32397437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Znamenskaya Church site |
E827848
|
entity |
| Predicate | associatedWithSquare |
P206264
|
FINISHED |
| Object | Vosstaniya Square |
E182290
|
NE 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: Vosstaniya Square | Statement: [Znamenskaya Church site, associatedWithSquare, Vosstaniya Square]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSquare Context triple: [Znamenskaya Church site, associatedWithSquare, Vosstaniya Square]
-
A.
associatedWithStand
Indicates a relationship where an entity is linked or connected to a particular stand, such as being located at, operating in, or otherwise related to that stand.
-
B.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
associatedWithBadge
Indicates that an entity has a connection or linkage to a specific badge, such as ownership, assignment, or display.
-
D.
associatedWithAddress
Indicates a relationship where an entity is linked or connected to a specific address.
-
E.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
- F. None of above. chosen
Provenance (5 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347b6d21a88190937022a2039f8852 |
completed | June 18, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:52 a.m.