Triple
T33855377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Crispin's Day |
E867757
|
entity |
| Predicate | actAndSceneOfSpeechInHenryV |
P177788
|
FINISHED |
| Object | Act 4 Scene 3 |
—
|
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: Act 4 Scene 3 | Statement: [Saint Crispin's Day, actAndSceneOfSpeechInHenryV, Act 4 Scene 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actAndSceneOfSpeechInHenryV Context triple: [Saint Crispin's Day, actAndSceneOfSpeechInHenryV, Act 4 Scene 3]
-
A.
placesShakespeareAs
Indicates that something assigns or interprets Shakespeare in a particular role, category, or position.
-
B.
engagementToHenryVIII
Indicates a formal betrothal or promise of marriage specifically to Henry VIII.
-
C.
roleInFalstaffArc
Indicates the specific function or contribution an entity has within the narrative or developmental arc associated with Falstaff.
-
D.
relationshipToPrinceHal
Indicates the specific familial, social, or interpersonal connection that an entity has to Prince Hal.
-
E.
roleDuringEnglishCivilWar
Indicates the specific function, position, or involvement an entity had during the period of the English Civil War.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:47 a.m.