Triple
T30545166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulvila |
E777391
|
entity |
| Predicate | regainedTownStatusYear |
P102909
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Ulvila, regainedTownStatusYear, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regainedTownStatusYear Context triple: [Ulvila, regainedTownStatusYear, 2000]
-
A.
grantedTownStatusInCentury
Indicates that an entity was officially granted town status during a specified century.
-
B.
reestablishedInYear
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
C.
recoveredTownStatusIn
chosen
Indicates that an entity has regained its status as a town within a specified jurisdiction or time period.
-
D.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
E.
constitutionalRestorationYear
Indicates the year in which a constitution was restored or reinstated after being suspended, replaced, or otherwise not in effect.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6888ec9608190b271bc0348b3d0e8 |
completed | May 2, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:19 p.m.