Triple
T22834317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stopnica |
E565899
|
entity |
| Predicate | previousTownStatusLost |
P120487
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Stopnica, previousTownStatusLost, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousTownStatusLost Context triple: [Stopnica, previousTownStatusLost, 19th century]
-
A.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
B.
recoveredTownStatusIn
Indicates that an entity has regained its status as a town within a specified jurisdiction or time period.
-
C.
previousMunicipalityStatus
Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
-
D.
lostRegionalCentreStatusTo
Indicates that one entity ceased to be a regional centre and that this status was subsequently assumed by another specified entity.
-
E.
lostTownStatusInCentury
chosen
Indicates that a settlement lost its official status as a town at some point during the specified century.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2d830881908d69929b854aad66 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.