Triple
T21465016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jezebel (play) |
E529571
|
entity |
| Predicate | notableAdaptationYear |
P144455
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [Jezebel (play), notableAdaptationYear, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAdaptationYear Context triple: [Jezebel (play), notableAdaptationYear, 1938]
-
A.
notableAdaptation
Indicates that one work is a significant adaptation or reinterpretation of another work.
-
B.
notableAdaptationElement
Indicates that one work is a significant adaptation or reinterpretation of another work.
-
C.
notableAdaptationType
Indicates that one work is a significant adaptation of another work in a specific way or medium (e.g., film adaptation, stage adaptation).
-
D.
notableAdaptationStudio
Indicates that a particular studio is especially recognized for creating an adaptation of the subject work or property.
-
E.
notableAdaptationContext
Indicates that an adaptation is particularly significant or noteworthy within a specific contextual setting (such as medium, time period, or cultural environment).
- F. None of above. chosen
Provenance (4 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f1b3cc819092c200f09c6f461e |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:09 p.m.