Triple
T3477157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SaveMoney |
E73400
|
entity |
| Predicate | collaborationStyle |
P42125
|
FINISHED |
| Object | frequent cross-member features on songs |
—
|
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: frequent cross-member features on songs | Statement: [SaveMoney, collaborationStyle, frequent cross-member features on songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationStyle Context triple: [SaveMoney, collaborationStyle, frequent cross-member features on songs]
-
A.
collaborationAspect
chosen
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
D.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
E.
cooperationType
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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb5a5cb88190be5624ae224e4c91 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.