Triple
T13487470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Anat |
E318542
|
entity |
| Predicate | hasParadoxicalCombination |
P20234
|
FINISHED |
| Object | virginity and extreme violence |
—
|
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: virginity and extreme violence | Statement: [Virgin Anat, hasParadoxicalCombination, virginity and extreme violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParadoxicalCombination Context triple: [Virgin Anat, hasParadoxicalCombination, virginity and extreme violence]
-
A.
paradoxType
chosen
Indicates the specific kind or category of paradox that characterizes the relationship or situation.
-
B.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
C.
paradoxName
Indicates that an entity is the name or label of a paradox associated with another entity.
-
D.
isSubtractiveCombination
Indicates that one entity is formed or derived by subtracting one or more components, values, or parts of another entity.
-
E.
hasFixedParityWith
Indicates that two entities share the same parity property (e.g., both even or both odd) and thus their parity remains consistently matched.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.