Triple
T28844274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musical Gifts |
E728406
|
entity |
| Predicate | featuresCollaborationType |
P19448
|
FINISHED |
| Object | duets |
—
|
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: duets | Statement: [Musical Gifts, featuresCollaborationType, duets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCollaborationType Context triple: [Musical Gifts, featuresCollaborationType, duets]
-
A.
featuresFamilyCollaboration
Indicates that there is a collaborative relationship or joint involvement between members of a family in a given context or activity.
-
B.
featuresWorkType
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
C.
supportsCollaborationFeature
Indicates that one entity provides or enables a collaboration-related feature for another entity or within a system.
-
D.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
E.
cooperationType
chosen
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: April 28, 2026, 6:41 a.m.