Triple
T32397336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Square of the Uprising |
E827845
|
entity |
| Predicate | hasUrbanRoleSince |
P30463
|
FINISHED |
| Object | Soviet era |
—
|
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: Soviet era | Statement: [Square of the Uprising, hasUrbanRoleSince, Soviet era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanRoleSince Context triple: [Square of the Uprising, hasUrbanRoleSince, Soviet era]
-
A.
hasUrbanRole
Indicates that an entity plays a specific functional or social role within an urban or city context.
-
B.
hasUrbanDistrictStatusSince
Indicates that an entity has held the legal or administrative status of an urban district continuously since a specified point in time.
-
C.
hasUrbanFunction
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
D.
urbanStatusSince
chosen
Indicates the point in time since which an entity has held an urban status or classification.
-
E.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c216aa9c819095e8268116230dd0 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.