Triple
T2079766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Bands |
E45210
|
entity |
| Predicate | subculture |
P21337
|
FINISHED |
| Object | Mummers String Band division |
—
|
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: Mummers String Band division | Statement: [String Bands, subculture, Mummers String Band division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subculture Context triple: [String Bands, subculture, Mummers String Band division]
-
A.
subgenre
Indicates that one genre is a more specific, subordinate category within a broader parent genre.
-
B.
subtradition
chosen
Indicates that one tradition is a specialized or derivative branch within a broader, overarching tradition.
-
C.
subtheme
Indicates that one topic or concept functions as a more specific, subordinate theme within a broader overarching theme.
-
D.
dominantCulture
Indicates that one culture holds prevailing power, influence, or normative status over others within a given social context.
-
E.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba3307308190ab329fe3192b2e0f |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.