Triple
T4589240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Catherine of Alexandria |
E103441
|
entity |
| Predicate | virginityStatusInLegend |
P28843
|
FINISHED |
| Object | consecrated virgin |
—
|
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: consecrated virgin | Statement: [Saint Catherine of Alexandria, virginityStatusInLegend, consecrated virgin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virginityStatusInLegend Context triple: [Saint Catherine of Alexandria, virginityStatusInLegend, consecrated virgin]
-
A.
refersToVirginity
chosen
Indicates that something is about or explicitly references the state or concept of virginity.
-
B.
sexStatus
Indicates whether and how a sexual relationship or sexual activity exists or has occurred between the related entities.
-
C.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
D.
romanticReputation
Indicates how an entity is perceived or regarded by others in the context of romantic behavior, history, or involvement.
-
E.
hasIncarnationsOfGender
Indicates that an entity has different incarnations or forms that each express or are associated with a particular gender.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592232888190af33c47636ca835d |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.