Triple
T19070013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bona Dea |
E466766
|
entity |
| Predicate | cultParticipantsExcluded |
P34541
|
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: [Bona Dea, cultParticipantsExcluded, men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultParticipantsExcluded Context triple: [Bona Dea, cultParticipantsExcluded, men]
-
A.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
B.
excludedFrom
chosen
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
excludesFromEvidence
Indicates that something is intentionally omitted or disallowed from being considered as evidence in a given context.
-
D.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
E.
endedParticipationOf
Indicates that one entity caused or marked the termination of another entity’s involvement in an activity, event, or relationship.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19caa708190876a2cb06aa0c9cc |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.