Triple
T29607920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Tetralogy |
E754627
|
entity |
| Predicate | dramaticSettingTime |
P20835
|
FINISHED |
| Object | 15th century England |
—
|
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: 15th century England | Statement: [First Tetralogy, dramaticSettingTime, 15th century England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticSettingTime Context triple: [First Tetralogy, dramaticSettingTime, 15th century England]
-
A.
timeOfSetting
chosen
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
B.
dramaticRequirement
Indicates that one entity is necessary or demanded by another in order to create, heighten, or sustain dramatic tension or effect.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de8aaf48190a2bc6177604a3771 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:26 p.m.