Triple
T25508216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book I (The Faerie Queene) |
E639301
|
entity |
| Predicate | vicePersonifiedBy |
P81304
|
FINISHED |
| Object | Duessa |
—
|
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: Duessa | Statement: [Book I (The Faerie Queene), vicePersonifiedBy, Duessa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vicePersonifiedBy Context triple: [Book I (The Faerie Queene), vicePersonifiedBy, Duessa]
-
A.
vice
Indicates a relationship where one entity serves as the deputy, subordinate leader, or second-in-command to another entity in a hierarchical structure.
-
B.
actsInSteadOf
Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
-
C.
ultimatePersona
Indicates that one entity represents the final, most complete, or most authoritative persona or identity of another entity.
-
D.
isPersonificationOf
chosen
Indicates that one entity represents or embodies an abstract concept, quality, or non-human thing in human form.
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69f5f80749f88190a5c2a70e7370003b |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:48 p.m.