Triple
T37725810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vril-ya |
E939714
|
entity |
| Predicate | settingPeriodOfText |
P123135
|
FINISHED |
| Object | 19th century speculative future |
—
|
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 speculative future | Statement: [Vril-ya, settingPeriodOfText, 19th century speculative future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingPeriodOfText Context triple: [Vril-ya, settingPeriodOfText, 19th century speculative future]
-
A.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
-
B.
mainSettingPeriod
chosen
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
setsBaselinePeriod
Indicates that an entity establishes or defines a reference time span used as the baseline for comparison, measurement, or evaluation of subsequent periods.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:18 p.m.