Triple
T33259081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Critic |
E851458
|
entity |
| Predicate | centralPlayWithinPlayTitle |
P61617
|
FINISHED |
| Object | The Spanish Armada |
—
|
NE NERFINISHED |
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: The Spanish Armada | Statement: [The Critic, centralPlayWithinPlayTitle, The Spanish Armada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPlayWithinPlayTitle Context triple: [The Critic, centralPlayWithinPlayTitle, The Spanish Armada]
-
A.
playWithinPlayTitle
chosen
Indicates that one play is presented as a play within another play, and this predicate gives the title of that embedded play.
-
B.
playsWithin
Indicates that one entity performs or takes place inside the spatial or temporal bounds of another entity.
-
C.
directsPlayWithinPlay
Indicates that one entity is responsible for directing a theatrical performance that occurs as a play within another play.
-
D.
containsPlayWithinPlay
Indicates that one play or dramatic work includes another play performed or depicted within its own narrative.
-
E.
playTitle
Indicates the title or name assigned to a play in a relationship between a play entity and its textual label.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 1:31 a.m.