Triple
T22146357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Coast Swing |
E547296
|
entity |
| Predicate | commonSocialSetting |
P43434
|
FINISHED |
| Object | ballroom socials |
—
|
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 socials | Statement: [East Coast Swing, commonSocialSetting, ballroom socials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSocialSetting Context triple: [East Coast Swing, commonSocialSetting, ballroom socials]
-
A.
socialBase
Indicates a foundational social relationship or structure that underlies or supports interactions between entities.
-
B.
socialFeature
Indicates that one entity provides or participates in a social interaction capability or function involving other entities.
-
C.
socialMedia
Indicates a relationship where one entity uses, is associated with, or interacts through social networking or content-sharing platforms with another entity.
-
D.
socialCenter
chosen
Indicates that a place functions as a primary gathering point or hub for social interaction and community activities.
-
E.
socialType
Indicates the category or nature of a social relationship or interaction that exists between entities.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f097248190a8a3cdff1593b5b5 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.