Triple
T32796511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrovskaya Ploshchad |
E838779
|
entity |
| Predicate | isHistoricalName |
P175129
|
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, isHistoricalName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricalName Context triple: [Petrovskaya Ploshchad, isHistoricalName, true]
-
A.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
B.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
C.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
D.
hasHistoricNameVariant
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
E.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
- F. None of above. chosen
Provenance (4 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_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:14 a.m.