Triple
T24016785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privislinsky Krai |
E594699
|
entity |
| Predicate | usedAsOfficialNameInPeriod |
P21988
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Privislinsky Krai, usedAsOfficialNameInPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsOfficialNameInPeriod Context triple: [Privislinsky Krai, usedAsOfficialNameInPeriod, late 19th century]
-
A.
officialNameDuringPeriod
chosen
Indicates that an entity had a specific official name that was valid only during a particular time period.
-
B.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
C.
usedAsOfficialTime
Indicates that something is employed as the recognized standard or authoritative reference for measuring time in an official context.
-
D.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
E.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a3f5a08190b7170270c4fcf080 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.