Triple
T864353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Deep Blue Sea |
E18667
|
entity |
| Predicate | dramaticStructure |
P3174
|
FINISHED |
| Object | three-act play |
—
|
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: three-act play | Statement: [The Deep Blue Sea, dramaticStructure, three-act play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticStructure Context triple: [The Deep Blue Sea, dramaticStructure, three-act play]
-
A.
dramaticForm
chosen
Indicates that one entity is expressed, structured, or realized in the form of a particular dramatic genre or theatrical mode.
-
B.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
-
C.
danceStructure
Indicates a structural or organizational relationship between elements within a dance, such as how movements, sections, or patterns are arranged and connected.
-
D.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
E.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac6956488190a5644cdd5b55684f |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.