Triple
T32803386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sound Theatre |
E838955
|
entity |
| Predicate | hasEnsembleFocus |
P191815
|
FINISHED |
| Object | small jazz 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: small jazz ensemble | Statement: [Sound Theatre, hasEnsembleFocus, small jazz ensemble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnsembleFocus Context triple: [Sound Theatre, hasEnsembleFocus, small jazz ensemble]
-
A.
hasProgramFocus
Indicates that an entity (such as a program or initiative) is oriented around or primarily concerned with a particular thematic area, topic, or objective.
-
B.
hasFocusGroup
Indicates that an entity is associated with or participates in a specific focus group for targeted discussion, feedback, or research.
-
C.
hasPrimaryInstrumentFocus
Indicates that an entity’s main emphasis or specialization is centered on a particular instrument.
-
D.
hasActingFocus
Indicates that an entity is the primary performer or focal agent carrying out an action in a given context.
-
E.
hasCollectionFocus
Indicates that something is primarily concerned with, centered on, or directed toward a particular collection or set of items.
- F. None of above. chosen
Provenance (4 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 1, 2026, 1:15 a.m.