Triple
T21979734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Town of Szczecin |
E542804
|
entity |
| Predicate | hasRestoredTownhouses |
P13045
|
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: [Old Town of Szczecin, hasRestoredTownhouses, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestoredTownhouses Context triple: [Old Town of Szczecin, hasRestoredTownhouses, true]
-
A.
hasReconstructedHouseOf
Indicates that one entity has rebuilt or restored the house that belongs or once belonged to another entity.
-
B.
recoveredTownStatusIn
Indicates that an entity has regained its status as a town within a specified jurisdiction or time period.
-
C.
hasRestoration
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
D.
restoredFamilyEstates
Indicates that an entity has taken action to return or reinstate previously held family-owned properties or estates to their original family or rightful heirs.
-
E.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248bdd88819098bfeca550608f14 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:03 p.m.