Triple
T10476154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | village of Wilanów |
E247048
|
entity |
| Predicate | urbanStatusChange |
P94235
|
FINISHED |
| Object | incorporated into Warsaw |
—
|
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: incorporated into Warsaw | Statement: [village of Wilanów, urbanStatusChange, incorporated into Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanStatusChange Context triple: [village of Wilanów, urbanStatusChange, incorporated into Warsaw]
-
A.
urbanStatusSince
Indicates the point in time since which an entity has held an urban status or classification.
-
B.
urbanRegenerationStatus
Indicates the current stage or condition of efforts to renew, redevelop, or revitalize an urban area.
-
C.
cityStatusContext
Indicates the contextual status or role that a city holds within a broader administrative, political, or situational framework.
-
D.
cityStatusUntil
Indicates the period up to a specified time during which a place holds or held a particular city status.
-
E.
urbanSuccessor
Indicates that one urban area directly follows or replaces another in a temporal or developmental sequence, serving as its successor in an urban context.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095021e081908dfaa467938c13fd |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:21 p.m.