Triple
T37828142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Chorus (UC Berkeley) |
E943121
|
entity |
| Predicate | auditioned |
P160209
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [University Chorus (UC Berkeley), auditioned, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auditioned Context triple: [University Chorus (UC Berkeley), auditioned, true]
-
A.
auditionedFor
chosen
Indicates that one entity formally tried out or performed in order to be considered for a role, position, or opportunity associated with another entity.
-
B.
audiation
Indicates the cognitive process of internally hearing, imagining, or understanding music without any external sound being physically present.
-
C.
heard
Indicates that one entity perceived a sound produced by another entity or source through hearing.
-
D.
audibleIn
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
-
E.
usedToOverhear
Indicates that one entity habitually or previously listened in on another entity’s conversations or activities without their knowledge.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.