Triple
T25507767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britomart |
E639290
|
entity |
| Predicate | roleInAllegory |
P77707
|
FINISHED |
| Object | ideal chaste woman |
—
|
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: ideal chaste woman | Statement: [Britomart, roleInAllegory, ideal chaste woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAllegory Context triple: [Britomart, roleInAllegory, ideal chaste woman]
-
A.
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).
-
B.
allegoricalRoleInInferno
Indicates a symbolic or allegorical function that an entity fulfills within the narrative framework of Dante’s Inferno.
-
C.
allegoryType
Indicates that one entity serves as a specific kind or category of allegory in relation to another entity.
-
D.
allegoricalDomain
Indicates that one entity serves as the abstract or symbolic domain that another entity allegorically represents or refers to.
-
E.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- 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_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 2:47 p.m.