Triple
T31459619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violent Playground |
E802550
|
entity |
| Predicate | timeInSetting |
P20835
|
FINISHED |
| Object | post-war Britain |
—
|
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: post-war Britain | Statement: [Violent Playground, timeInSetting, post-war Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInSetting Context triple: [Violent Playground, timeInSetting, post-war Britain]
-
A.
timeOfSetting
chosen
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
B.
timeSettingVariant
Indicates a relationship where one time setting is an alternative or modified version of another time setting.
-
C.
timeProperty
Indicates that one entity specifies, constrains, or characterizes a temporal aspect or timing-related attribute of another entity.
-
D.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
E.
timeOfSettingEnd
Indicates the point in time at which a specified setting, condition, or configuration ceases to be in effect.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 9:19 p.m.