Triple
T9602533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wench Brigades |
E231882
|
entity |
| Predicate | traditionallyInclude |
P44882
|
FINISHED |
| Object | alcohol-fueled revelry |
—
|
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: alcohol-fueled revelry | Statement: [Wench Brigades, traditionallyInclude, alcohol-fueled revelry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyInclude Context triple: [Wench Brigades, traditionallyInclude, alcohol-fueled revelry]
-
A.
traditionallyIncludes
chosen
Indicates that something customarily or historically contains or incorporates something else as a standard or expected part.
-
B.
traditionIncludes
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
-
C.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5af8f0819089408ed630afa812 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.