Triple
T2490822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novoslobodskaya |
E52035
|
entity |
| Predicate | artworkLocation |
P25947
|
FINISHED |
| Object | end of the central hall |
—
|
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: end of the central hall | Statement: [Novoslobodskaya, artworkLocation, end of the central hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artworkLocation Context triple: [Novoslobodskaya, artworkLocation, end of the central hall]
-
A.
rockArtLocationType
Indicates the specific type or category of location where rock art is found or situated.
-
B.
artworkBy
Indicates that one entity is the creator or artist responsible for producing the other entity as an artwork.
-
C.
famousArtworkLocatedIn
chosen
Indicates that a specific famous artwork is physically situated or displayed within a particular location or venue.
-
D.
placeOfDepiction
Indicates the location or setting where the depicted subject is shown as being situated in the representation.
-
E.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd18fe32081909580c6272a6013c5 |
completed | March 7, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69abd0b980b481908d4932bcea4a6167 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.