Triple
T9958305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian State Historical Archive |
E195498
|
entity |
| Predicate | mainPeriodCovered |
P3058
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Russian State Historical Archive, mainPeriodCovered, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPeriodCovered Context triple: [Russian State Historical Archive, mainPeriodCovered, 18th century]
-
A.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
C.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
D.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
E.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6cec7dc8190bb7e43c82a317707 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.