Triple
T3937745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Opera Chorus |
E90954
|
entity |
| Predicate | auditionPolicy |
P58
|
FINISHED |
| Object | professional auditioned ensemble |
—
|
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: professional auditioned ensemble | Statement: [Metropolitan Opera Chorus, auditionPolicy, professional auditioned ensemble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auditionPolicy Context triple: [Metropolitan Opera Chorus, auditionPolicy, professional auditioned ensemble]
-
A.
admissionPolicy
chosen
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
B.
decisionPublicationPolicy
Indicates the policy or rules governing how decisions are made public or communicated.
-
C.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
D.
ordinationPolicy
Indicates the rules or criteria governing how entities are ordered, ranked, or arranged relative to one another.
-
E.
supportsAudioQuality
Indicates that one entity provides or is compatible with a specified level or type of audio quality for another entity or 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedcfd7d48190bbacee8b5b1b5070 |
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:24 p.m.