Triple
T25508377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book VI |
E639305
|
entity |
| Predicate | containsAllegoryOf |
P77707
|
FINISHED |
| Object | Elizabethan courtly behavior |
—
|
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: Elizabethan courtly behavior | Statement: [Book VI, containsAllegoryOf, Elizabethan courtly behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAllegoryOf Context triple: [Book VI, containsAllegoryOf, Elizabethan courtly behavior]
-
A.
containsAllusion
Indicates that one entity includes or incorporates an indirect reference or allusion to another entity.
-
B.
allegoricalInterpretation
chosen
Indicates that one entity is interpreted as symbolically representing deeper, often moral or spiritual, meanings within another entity (such as a text, image, or event).
-
C.
hasAllegoricalFigures
Indicates that a work, scene, or element includes figures that symbolically represent abstract ideas, concepts, or moral qualities.
-
D.
hasAllegoricalDepictionsBy
Indicates that one entity is represented through allegorical depictions created by another entity.
-
E.
allegoryType
Indicates that one entity serves as a specific kind or category of allegory in relation to another entity.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 21, 2026, 2:48 p.m.