Triple
T35195496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICCAs |
E1016245
|
entity |
| Predicate | featuredActivity |
P8834
|
FINISHED |
| Object | collegiate a cappella |
—
|
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: collegiate a cappella | Statement: [ICCAs, featuredActivity, collegiate a cappella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredActivity Context triple: [ICCAs, featuredActivity, collegiate a cappella]
-
A.
modernActivities
Indicates that the associated activities are contemporary or characteristic of the modern era, as opposed to traditional or historical practices.
-
B.
featuresEventsFor
Indicates that something presents, highlights, or includes specific events as part of its content or offering.
-
C.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
D.
activityType
chosen
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
notableActivityIn
Indicates that an entity is particularly recognized for performing a significant activity within a specified place, context, or domain.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.