Triple
T3935962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appleton |
E90912
|
entity |
| Predicate | culturalActivity |
P2955
|
FINISHED |
| Object | performing arts |
—
|
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: performing arts | Statement: [Appleton, culturalActivity, performing arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalActivity Context triple: [Appleton, culturalActivity, performing arts]
-
A.
hasCulturalEvent
chosen
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
B.
culturalOrganization
Indicates that an entity is an organization whose primary purpose involves cultural activities, preservation, or promotion.
-
C.
hasCulturalOrganization
Indicates that an entity possesses, is associated with, or hosts a cultural organization (such as a museum, arts group, or cultural institution).
-
D.
culturalMovement
Indicates that an entity is associated with, participates in, or belongs to a particular cultural movement or trend.
-
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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcd29148190a98e4549c9ed8888 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.