Triple
T33340987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pure/Honey |
E853665
|
entity |
| Predicate | featuresCulturalElement |
P3114
|
FINISHED |
| Object | ballroom chants |
—
|
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: ballroom chants | Statement: [Pure/Honey, featuresCulturalElement, ballroom chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCulturalElement Context triple: [Pure/Honey, featuresCulturalElement, ballroom chants]
-
A.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
B.
hasCulturalFeature
chosen
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
C.
cultureCharacteristic
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
D.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
E.
hasCulturalFunction
Indicates that something serves a particular role, purpose, or function within a culture or cultural 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01a18e350481909f848686568d19bc |
completed | May 11, 2026, 9:29 a.m. |
| PD | Predicate disambiguation | batch_6a01a121b67c81908a6c5be9eb8e9ca5 |
completed | May 11, 2026, 9:28 a.m. |
Created at: May 1, 2026, 1:34 a.m.