Triple
T8088759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorokhovaya Street |
E188800
|
entity |
| Predicate | hasHistoricalBuildings |
P42084
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gorokhovaya Street, hasHistoricalBuildings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalBuildings Context triple: [Gorokhovaya Street, hasHistoricalBuildings, yes]
-
A.
hasPreservedBuildings
chosen
Indicates that an entity possesses buildings that have been maintained or kept in their original or historical condition.
-
B.
hasHistoricChurches
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
-
C.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
D.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
E.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
- 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_69ca82b7b3e88190b9041ab0ef28b3cb |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb421c717c819089dd88c30a6401aa |
completed | March 31, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.