Triple
T38388744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act III (Le Martyre de saint Sébastien) |
E899650
|
entity |
| Predicate | hasParentWorkForm |
P58459
|
FINISHED |
| Object | mystery 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: mystery play | Statement: [Act III (Le Martyre de saint Sébastien), hasParentWorkForm, mystery play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentWorkForm Context triple: [Act III (Le Martyre de saint Sébastien), hasParentWorkForm, mystery play]
-
A.
hasParentWork
Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
-
B.
hasWorkForm
chosen
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
-
C.
hasParentWorkKey
Indicates that an entity is associated with the identifier (key) of the parent work from which it is derived or of which it is a part.
-
D.
hasChildInWork
Indicates that one entity has a child who appears or is represented within the other entity’s work or creation.
-
E.
hasParentWorkComposer
Indicates that a work is related to the composer of its parent (containing or overarching) work.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.