Triple
T30846682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Arte |
E785652
|
entity |
| Predicate | releasesFeature |
P157171
|
FINISHED |
| Object | prominent classical performers |
—
|
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: prominent classical performers | Statement: [Pro Arte, releasesFeature, prominent classical performers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasesFeature Context triple: [Pro Arte, releasesFeature, prominent classical performers]
-
A.
featureOfReleases
chosen
Indicates that certain features are associated with, included in, or introduced as part of specific releases.
-
B.
releases
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
-
C.
launchedFeature
Indicates that an entity has released or made a particular feature available for use.
-
D.
releasesInclude
Indicates that a particular release or distribution contains, bundles, or makes available the specified component, item, or content.
-
E.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:46 p.m.