Triple
T33659130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Kalvan of Otherwhen |
E862302
|
entity |
| Predicate | timePeriodInSetting |
P123135
|
FINISHED |
| Object | early gunpowder era analogue |
—
|
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: early gunpowder era analogue | Statement: [Lord Kalvan of Otherwhen, timePeriodInSetting, early gunpowder era analogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodInSetting Context triple: [Lord Kalvan of Otherwhen, timePeriodInSetting, early gunpowder era analogue]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
-
C.
mainSettingPeriod
chosen
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
timeSettingVariant
Indicates a relationship where one time setting is an alternative or modified version of another time setting.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:42 a.m.