Triple
T1463624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeiparthenos |
E31568
|
entity |
| Predicate | refersToVirginity |
P28843
|
FINISHED |
| Object | before the birth of Jesus |
—
|
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: before the birth of Jesus | Statement: [Aeiparthenos, refersToVirginity, before the birth of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToVirginity Context triple: [Aeiparthenos, refersToVirginity, before the birth of Jesus]
-
A.
hasSex
Indicates that one entity engages in sexual activity with another entity.
-
B.
coneSex
Indicates a sexual or mating relationship involving a cone-shaped structure or entity.
-
C.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
D.
usesConfessions
Indicates that one entity employs or relies on another entity’s confessions as a basis for some action, decision, or outcome.
-
E.
usesConfession
Indicates that one entity employs or relies on a confession (typically an admission of guilt or wrongdoing) as part of its actions or reasoning toward another entity or outcome.
- F. None of above. chosen
Provenance (4 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.