Triple
T23526301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demeter’s cult |
E576441
|
entity |
| Predicate | allowedInitiates |
P273
|
FINISHED |
| Object | men |
—
|
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: men | Statement: [Demeter’s cult, allowedInitiates, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedInitiates Context triple: [Demeter’s cult, allowedInitiates, men]
-
A.
admittedInitiatesFrom
Indicates that an admission event initiates or originates from a particular source, cause, or prior action.
-
B.
hasInitiation
Indicates that one entity initiates, starts, or triggers an action, process, or relationship involving another entity.
-
C.
possiblyInitiatedBy
Indicates that an event or state may have been initiated or caused by a particular entity, but this initiating role is uncertain or not definitively established.
-
D.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac73be64819083e4a1c2c09551fb |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.