Triple
T9716875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vestal Virgins |
E235162
|
entity |
| Predicate | endOfInstitutionDate |
P90406
|
FINISHED |
| Object | late 4th century CE |
—
|
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: late 4th century CE | Statement: [Vestal Virgins, endOfInstitutionDate, late 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfInstitutionDate Context triple: [Vestal Virgins, endOfInstitutionDate, late 4th century CE]
-
A.
educationEndTime
Indicates the point in time at which an entity’s period of education or study is completed or ends.
-
B.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
E.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3d75e08190b4d86363595bd40d |
completed | April 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:20 p.m.