Triple
T36806398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesione Hushabye |
E909464
|
entity |
| Predicate | playSettingPeriod |
P123135
|
FINISHED |
| Object | World War I era |
—
|
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: World War I era | Statement: [Hesione Hushabye, playSettingPeriod, World War I era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playSettingPeriod Context triple: [Hesione Hushabye, playSettingPeriod, World War I era]
-
A.
mainSettingPeriod
chosen
Indicates the historical or temporal period in which the primary setting of a work or event takes place.
-
B.
programStartPeriod
Indicates the time interval during which a program is initially scheduled to begin or become active.
-
C.
playTime
Indicates the duration or specific time period during which an entity engages in playing or recreational activity with another entity or object.
-
D.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:13 p.m.